All connectors
Implemented
HR, recruitment & payroll
Ashby logo

Ashby

Read and write Ashby candidates, notes, tags, applications, stage changes and custom field values, and read jobs, postings, interviews and offers.

Automate sourcing intake and pipeline moves in Ashby and pass hires and recruiting data to HRIS and analytics.

Source actions

18

Destination actions

7

Data types

17

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

application stage
  • Change application stage
    Destination
    Duplicate protected

    Moves an application to an interview stage; an archive reason is required when the target is an archived stage. No email is sent.

applications
  • Add candidate to job
    Destination
    Not retried automatically

    Considers an existing candidate for a job, optionally in a given stage.

  • Get application
    Source

    One application by ID.

  • List applications
    Source
    Incremental

    Applications with stage, status, job and hiring team, or only those changed since a sync token.

archive reasons
  • List archive reasons
    Source

    Archive reasons for archiving applications.

candidate notes
  • Add candidate note
    Destination
    Not retried automatically

    Adds a plain-text or HTML note to a candidate without notifying users.

  • List candidate notes
    Source

    Notes on a candidate, newest first.

candidate tags
  • Tag candidate
    Destination
    Duplicate protected

    Adds an existing tag to a candidate.

candidates
  • Create candidate
    Destination
    Not retried automatically

    Creates a candidate with contact details, source and location.

  • Get candidate
    Source

    One candidate by ID.

  • List candidates
    Source
    Incremental

    All candidates, or only those changed since the last sync token.

  • Search candidates
    Source

    Finds candidates by email and/or name.

  • Update candidate
    Destination
    Duplicate protected

    Updates candidate contact details, source or location without notifying users.

custom field values
  • Set custom field value
    Destination
    Duplicate protected

    Sets one custom field on an application, candidate, job or opening.

custom fields
  • List custom fields
    Source
    Incremental

    Custom field definitions with object type, field type and selectable values.

departments
  • List departments
    Source
    Incremental

    Departments with parent hierarchy.

interview schedules
  • List interview schedules
    Source
    Incremental

    Interview schedules with their events, interviewers and times.

interview stages
  • List interview stages
    Source

    Stages of one interview plan in order; use their IDs for stage changes.

job postings
  • List job postings
    Source

    Published job postings with location, department and apply link.

jobs
  • Get job
    Source

    One job by ID.

  • List jobs
    Source
    Incremental

    Jobs with status, department, location, hiring team and custom fields.

locations
  • List locations
    Source
    Incremental

    Office locations with address and workplace type.

offers
  • List offers
    Source
    Incremental

    Offers with status and decision (read-only; salary is not returned).

sources
  • List sources
    Source

    Candidate sources with their source type.

users
  • List users
    Source
    Incremental

    Ashby users with role and status.

Authentication

Ashby API key (HTTP Basic, empty password)

Plans and access

API keys are available to Ashby customers; an Ashby admin creates them. Each key has module permissions (for example candidatesRead, candidatesWrite, jobsRead, hiringProcessMetadataRead); confidential jobs need explicit access.

Test environment

Ashby provides demo data and sandbox organisations to customers and partners on request.

Rate limits

Ashby rate limits per API key and returns HTTP 429 when exceeded; the limit values are not published in the API reference.

Provider events

Webhooks for application, candidate, interview, offer and job events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Ashby returns HTTP 200 with success false for many errors; Nexra converts these to validation, permission or not-found errors.
  • Offers are read-only and salary values are not returned.
  • Archiving through a stage change never sends an archive email.
  • File and resume uploads, application transfers, interview scheduling writes and deletes are not implemented.
  • Candidate, application and note creates have no idempotency key; uncertain writes are not repeated automatically.
  • Rate limit values are not documented in the public reference (unverified).