Ashby

Integrate Ashby applicant tracking into your workflows to list, create, and update candidates, query job postings, and filter applications. Use it to automate hiring pipelines — from sourcing candidates to tracking offer stages.

Overview

Operations

Configuration

Outputs

Candidate outputs (ashby_get_candidate, ashby_create_candidate, ashby_update_candidate)

List candidates outputs (ashby_list_candidates)

List applications outputs (ashby_list_applications)

Application object fields:

Job posting outputs (ashby_get_job_postings)

Example

[Starter] → [Ashby: List Candidates] → [Agent: summarize new hires] → [Slack: post digest]

Connect an API key stored as {{ASHBY_API_KEY}} and set createdAfter to {{starter.since}} to pull only candidates added since a given date. The Agent block receives {{ashby.candidates}} and produces a summary, which a Slack block then posts to a recruiting channel.

Tips

• API key auth — Ashby uses HTTP Basic Auth with your API key as the username and an empty password. The integration encodes this automatically; you only need to supply the raw key value.
• Pagination — Both list operations return moreDataAvailable and nextCursor. Chain a second Ashby block with cursor set to {{ashby.nextCursor}} to fetch the next page inside a loop block.
• Status filters — When listing applications, the status param accepts exactly Active, Hired, Archived, or Lead. Any other value is silently ignored by the Ashby API.
• Expand job details — Set expandJob to true on ashby_get_job_postings to receive the full nested job object alongside the posting, saving a separate lookup call.
• Backdating records — Both create and update candidate support createdAt for importing historical data. The update operation can only change createdAt if the record was originally created with a backdated timestamp.