ceven

Ashby

Syncs candidate pipeline changes to your team chat, automates interview scheduling logistics, and pushes hiring metrics into your reporting dashboards.

Try Ashby in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Ashby integration

    • Describe the outcome and Ceven picks the right Ashby calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Ashby data, across all 125 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Ashby access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Ashby, when, and on whose behalf.
    • The agent pauses and asks when Ashby is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Ashby.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Ashby action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Ashby, and when to use it.

Create candidate
Use this when you find a profile on LinkedIn or another source and need to add them to the Ashby pipeline immediately.
Update candidate stage
Move a candidate to a new stage in the hiring process, such as moving from phone screen to onsite.
Get candidate details
Pull the full profile for a candidate, including their current stage, resume link, and application date.
Search candidates
Query the candidate database by name, email, or specific skill tags to find previous applicants.
Create interview
Schedule a new interview event for a candidate and link it to a specific job opening.
List job openings
Pull all active job postings to ensure the agent is mapping candidates to the correct open roles.
Add candidate note
Post a comment or internal note to a candidate profile based on an external conversation or email.
Get interview scorecards
Pull all submitted feedback for a specific candidate to summarize strengths and weaknesses for a manager.
Create offer
Initiate the offer process by creating an offer record with salary and equity details.
List applications
Pull a list of all applications for a specific job, filtered by date or source.
Update job status
Change a job opening from open to filled or paused to stop new candidate flow.
Get candidate activity
Pull the audit log of all changes made to a candidate record to see who last touched the profile.

12 actions · scroll to see them all

Frequently asked questions

Ceven operates using the permissions assigned to the API key or OAuth token used during connection. If the connected user does not have permission to view sensitive salary data or specific job folders within Ashby, the Ceven agent will receive a forbidden error from the API. This ensures that your internal privacy settings are respected. If you find that an agent cannot move a candidate or read a note, check that the admin user who authorized the connection has the appropriate role in Ashby to perform those specific actions. You can manage these permissions directly in your Ashby settings panel without needing to reconnect the entire integration.
Yes. Ceven can interact with the Ashby interview API to create events and link them to candidates. However, it is important to note that Ashby relies on integrated calendars for actual availability. Ceven pulls the availability data through Ashby and then pushes the event. If there is a calendar conflict that Ashby does not catch, the event may still be created but will show as a conflict in the user's calendar. We recommend using the agent to draft the invite and then having a human confirm the final slot for high touch executive roles to avoid scheduling mishaps.
Ceven can perform bulk updates by iterating through a list of candidates and calling the update endpoint for each. However, Ashby imposes strict rate limits on their API to ensure platform stability. If you attempt to move five hundred candidates at once, the agent will automatically implement a backoff strategy, pausing between calls to avoid hitting the limit. For very large migrations, we suggest scheduling the workflow to run in batches over several hours. This prevents your API key from being temporarily throttled, which would otherwise pause all other active recruiting workflows.
When you ask Ceven to summarize a candidate, it pulls all existing notes and scorecards from Ashby. The model then identifies recurring themes, such as technical proficiency or culture fit, and presents them as a bulleted list. The agent does not alter the original notes in Ashby; it only reads them to provide the summary. If you want the agent to write a new note back into Ashby, you must explicitly use an action like Add candidate note. This ensures your primary system of record remains clean and only contains intentional human or agent entries.
Yes. By using the List applications and Get candidate activity actions, Ceven can calculate the time it takes for candidates to move between stages. You can set up a weekly workflow that pulls this data for every open role and sends a summary to your leadership team. The agent can identify bottlenecks, such as a specific interview stage where candidates linger for more than five days. This allows you to pinpoint exactly where the process is slowing down without having to build a custom report inside the Ashby analytics dashboard every week.
Ceven can trigger email notifications if they are tied to stage changes or specific Ashby events. However, for custom one off emails, the agent typically drafts the content and places it in your communication tool or creates a task for the recruiter to send the email via the Ashby portal. This is because Ashby manages email deliverability and threading through its own internal mail servers. By keeping the actual sending process within Ashby, you ensure that all candidate correspondence is perfectly archived in the candidate timeline for future reference by the whole team.
If a job is deleted, any agent attempting to update a candidate associated with that job will receive a not found error from the Ashby API. Ceven handles this by catching the error and notifying the workflow owner via a system alert. The agent will not crash or loop infinitely; it simply marks that specific candidate update as failed and moves to the next item in the queue. We recommend periodically syncing your list of active jobs to ensure that your automated triggers are only running for roles that are still actively recruiting.
Absolutely. You can build a workflow that triggers on a schedule, such as every Monday morning, to pull a list of all candidates who reached the final stage in the last seven days. Ceven then maps those Ashby fields to the columns in a Google Sheet or Excel file. This is particularly useful for teams that need to share high level hiring progress with stakeholders who do not have direct access to the Ashby platform. The agent handles the data mapping and ensures that duplicate entries are updated rather than added as new rows.

Alternatives to Ashby

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Greenhouse logoGreenhouseLever logoLeverWorkable logoWorkable

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Ashby and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free