Ashby
ashbyAshby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process
Triggers (28)
Los triggers son eventos externos que pueden iniciar un flujo en tus agentes (ej: nuevo email, mensaje recibido, registro creado).
Application Signature Request UpdatedASHBY_APPLICATION_SIGNATURE_REQUEST_UPDATEDTriggerTriggers when an e-signature request attached to an application — an NDA, a consent form — is sent, cancelled, completed or deleted. Signature requests on offer letters are a separate trigger, because Ashby gives the two different fields.
ASHBY_APPLICATION_SIGNATURE_REQUEST_UPDATEDTriggerTriggers when an e-signature request attached to an application — an NDA, a consent form — is sent, cancelled, completed or deleted. Signature requests on offer letters are a separate trigger, because Ashby gives the two different fields.
Configuración
event_typestringenumOnly fire on this point in the signature request's life. Ashby delivers one event per point, so leaving this unset means four deliveries per request; `completed` means the document came back signed.
sentcancelledcompleteddeleted
Payload del evento
applicationIdstringObligatorioId of the application the document belongs to.
eventTypestringenumWhat happened to the signature request. `completed` means the document came back signed.
sentcancelledcompleteddeleted
Application SubmittedASHBY_APPLICATION_SUBMITTEDTriggerTriggers when a candidate submits an application, or a recruiter adds one by hand. Does not fire for bulk imports or integration syncs, and does not fire when an existing application later changes.
ASHBY_APPLICATION_SUBMITTEDTriggerTriggers when a candidate submits an application, or a recruiter adds one by hand. Does not fire for bulk imports or integration syncs, and does not fire when an existing application later changes.
Configuración
job_titlestringOnly fire for applications on the job with this exact title, e.g. `Senior Backend Engineer`. Matched exactly and case-sensitively; use `ASHBY_LIST_JOBS` to find your job titles. Leave unset to fire for every job.
Payload del evento
applicationobjectObligatorioThe application, with its candidate, job and current stage.
Application UpdatedASHBY_APPLICATION_UPDATEDTriggerTriggers when anything on an existing application changes — its fields, custom fields, archive state, or the job it is transferred to. Also fires alongside a hire and alongside a stage change, so enabling those triggers too gives two deliveries per action.
ASHBY_APPLICATION_UPDATEDTriggerTriggers when anything on an existing application changes — its fields, custom fields, archive state, or the job it is transferred to. Also fires alongside a hire and alongside a stage change, so enabling those triggers too gives two deliveries per action.
Configuración
application_statusstringenumOnly fire when the application's status after the change is this one. This is the resulting status, not a transition, so an already-archived application that is edited again fires again with `Archived`. Leave unset to fire for every status.
HiredArchivedActiveLeadjob_titlestringOnly fire for applications on the job with this exact title, e.g. `Senior Backend Engineer`. Matched exactly and case-sensitively; use `ASHBY_LIST_JOBS` to find your job titles. Leave unset to fire for every job.
Payload del evento
applicationobjectObligatorioThe application after the change. Ashby sends no before/after diff, so which field changed is not stated.
Candidate DeletedASHBY_CANDIDATE_DELETEDTriggerTriggers when a candidate record is deleted from Ashby. Distinct from a merge, where the candidate's history is folded into another record rather than lost.
ASHBY_CANDIDATE_DELETEDTriggerTriggers when a candidate record is deleted from Ashby. Distinct from a merge, where the candidate's history is folded into another record rather than lost.
Configuración
Sin parámetros.
Payload del evento
candidateobjectObligatorioThe deleted candidate, by id only. Nothing else survives the deletion, so the id no longer resolves against Ashby.
Candidate Emails ChangedASHBY_CANDIDATE_EMAILS_CHANGEDTriggerTriggers when a candidate's recent email messages may have changed. Carries no message content — use the watermark in the payload to refetch them; Ashby marks this webhook beta and may not enable it for every organisation.
ASHBY_CANDIDATE_EMAILS_CHANGEDTriggerTriggers when a candidate's recent email messages may have changed. Carries no message content — use the watermark in the payload to refetch them; Ashby marks this webhook beta and may not enable it for every organisation.
Configuración
Sin parámetros.
Payload del evento
candidateobjectObligatorioThe candidate whose recent email messages should be refreshed.
observedAtstringISO 8601 timestamp Ashby observed the change. Informational only.
watermarkstringObligatorioOpaque token for the refresh. Pass it unchanged, with no cursor, to Ashby's `candidate.getRecentEmailMessages` within one hour — only a request carrying it is guaranteed to include the change that produced this event. After an hour it fails with `watermark_expired`. The API key doing the fetch needs the `emails:read` scope. Deliveries can be duplicated or arrive out of order, and a delayed retry carries a new watermark.
Candidate HiredASHBY_CANDIDATE_HIREDTriggerTriggers when a candidate is marked hired in Ashby, including hires on confidential jobs. Pushing that hire to an HRIS is a separate, later trigger.
ASHBY_CANDIDATE_HIREDTriggerTriggers when a candidate is marked hired in Ashby, including hires on confidential jobs. Pushing that hire to an HRIS is a separate, later trigger.
Configuración
job_titlestringOnly fire for applications on the job with this exact title, e.g. `Senior Backend Engineer`. Matched exactly and case-sensitively; use `ASHBY_LIST_JOBS` to find your job titles. Leave unset to fire for every job.
Payload del evento
applicationobjectObligatorioThe application, now in its hired state.
offerobjectAn offer process attached to an application.
Candidate MergedASHBY_CANDIDATE_MERGEDTriggerTriggers when two candidate records are merged into one. Like a deletion this is the only way to observe it, but unlike a deletion the candidate's history survives on the record named here.
ASHBY_CANDIDATE_MERGEDTriggerTriggers when two candidate records are merged into one. Like a deletion this is the only way to observe it, but unlike a deletion the candidate's history survives on the record named here.
Configuración
Sin parámetros.
Payload del evento
deletedCandidateobjectObligatorioThe candidate that was merged away. Its id no longer resolves in Ashby — repoint anything you hold against it at `mergedCandidate`.
mergedCandidateobjectObligatorioThe candidate that survived the merge and now holds both histories.
Candidate Moved To Interview StageASHBY_CANDIDATE_MOVED_TO_INTERVIEW_STAGETriggerTriggers when an application moves into a different interview stage, in either direction. Ashby also emits an application-updated event for the same move, and emits this one itself when a candidate is hired.
ASHBY_CANDIDATE_MOVED_TO_INTERVIEW_STAGETriggerTriggers when an application moves into a different interview stage, in either direction. Ashby also emits an application-updated event for the same move, and emits this one itself when a candidate is hired.
Configuración
interview_stage_titlestringOnly fire when the application moves into the stage with this exact title, e.g. `Onsite`. Matched exactly and case-sensitively; use `ASHBY_LIST_INTERVIEW_STAGES` to find a job's stage titles. Leave unset to fire for every stage.
job_titlestringOnly fire for applications on the job with this exact title, e.g. `Senior Backend Engineer`. Matched exactly and case-sensitively; use `ASHBY_LIST_JOBS` to find your job titles. Leave unset to fire for every job.
Payload del evento
applicationobjectObligatorioThe application after the move. `currentInterviewStage` is the stage it moved into; Ashby does not send the stage it left, so a move backwards is indistinguishable from a move forwards.
Candidate Pushed To HRISASHBY_CANDIDATE_PUSHED_TO_HRISTriggerTriggers when a hired candidate is pushed from Ashby into an HRIS. This is the explicit downstream hand-off, which can follow the hire itself by minutes or days; the hire fires the candidate-hired trigger.
ASHBY_CANDIDATE_PUSHED_TO_HRISTriggerTriggers when a hired candidate is pushed from Ashby into an HRIS. This is the explicit downstream hand-off, which can follow the hire itself by minutes or days; the hire fires the candidate-hired trigger.
Configuración
job_titlestringOnly fire for applications on the job with this exact title, e.g. `Senior Backend Engineer`. Matched exactly and case-sensitively; use `ASHBY_LIST_JOBS` to find your job titles. Leave unset to fire for every job.
Payload del evento
applicationobjectObligatorioThe application the pushed candidate was hired through.
Interview Schedule CreatedASHBY_INTERVIEW_SCHEDULE_CREATEDTriggerTriggers when an interview loop is first booked for an application. Ashby also emits an interview-schedule-updated event for the same booking, so enabling both gives two deliveries.
ASHBY_INTERVIEW_SCHEDULE_CREATEDTriggerTriggers when an interview loop is first booked for an application. Ashby also emits an interview-schedule-updated event for the same booking, so enabling both gives two deliveries.
Configuración
Sin parámetros.
Payload del evento
interviewScheduleobjectObligatorioThe schedule, with every interview event booked within it.
Interview Schedule UpdatedASHBY_INTERVIEW_SCHEDULE_UPDATEDTriggerTriggers when a booked interview loop changes, including a change to one interview inside it. Also fires once when the loop is first booked, alongside the interview-schedule-created trigger.
ASHBY_INTERVIEW_SCHEDULE_UPDATEDTriggerTriggers when a booked interview loop changes, including a change to one interview inside it. Also fires once when the loop is first booked, alongside the interview-schedule-created trigger.
Configuración
Sin parámetros.
Payload del evento
interviewScheduleobjectObligatorioThe schedule after the change, with every interview event booked within it. Ashby sends no before/after diff, so which event moved is not stated.
Job CreatedASHBY_JOB_CREATEDTriggerTriggers when a job — the internal requisition, not its public posting — is created. Confidential jobs are never delivered.
ASHBY_JOB_CREATEDTriggerTriggers when a job — the internal requisition, not its public posting — is created. Confidential jobs are never delivered.
Configuración
Sin parámetros.
Payload del evento
jobobjectObligatorioThe job, with its hiring team, interview plans and custom fields.
Job Interview Plan SwitchedASHBY_JOB_INTERVIEW_PLAN_SWITCHEDTriggerTriggers when a job is moved onto a different interview plan, remapping the stages of every application in flight. Ashby also emits a job-updated event for the same switch.
ASHBY_JOB_INTERVIEW_PLAN_SWITCHEDTriggerTriggers when a job is moved onto a different interview plan, remapping the stages of every application in flight. Ashby also emits a job-updated event for the same switch.
Configuración
Sin parámetros.
Payload del evento
fromInterviewPlanobjectAn interview plan, by id and title.
interviewStageMappingsobject[]How each stage of the old plan maps onto a stage of the new one. Applications in flight were moved along these pairs.
jobIdstringId of the job whose interview plan was switched.
toInterviewPlanobjectAn interview plan, by id and title.
Job Posting DeletedASHBY_JOB_POSTING_DELETEDTriggerTriggers when a job posting is deleted. Taking a posting off its job board without deleting it fires the job-posting-unpublished trigger instead.
ASHBY_JOB_POSTING_DELETEDTriggerTriggers when a job posting is deleted. Taking a posting off its job board without deleting it fires the job-posting-unpublished trigger instead.
Configuración
Sin parámetros.
Payload del evento
jobPostingobjectObligatorioThe deleted posting, by id. Its own id no longer resolves against Ashby, but `jobId` still points at the job it advertised.
Job Posting PublishedASHBY_JOB_POSTING_PUBLISHEDTriggerTriggers when a job posting is published to a job board. Ashby also emits a job-posting-updated event for the same publish, so enabling both gives two deliveries.
ASHBY_JOB_POSTING_PUBLISHEDTriggerTriggers when a job posting is published to a job board. Ashby also emits a job-posting-updated event for the same publish, so enabling both gives two deliveries.
Configuración
department_namestringOnly fire for postings in the department with this exact name, e.g. `Engineering`. Matched exactly and case-sensitively; use `ASHBY_LIST_DEPARTMENTS` to find your department names. Leave unset to fire for every department.
Payload del evento
jobPostingobjectObligatorioThe posting as published, with its apply link and compensation summary.
Job Posting UnpublishedASHBY_JOB_POSTING_UNPUBLISHEDTriggerTriggers when a job posting is removed from its job board but kept in Ashby. Deleting the posting outright fires the job-posting-deleted trigger instead.
ASHBY_JOB_POSTING_UNPUBLISHEDTriggerTriggers when a job posting is removed from its job board but kept in Ashby. Deleting the posting outright fires the job-posting-deleted trigger instead.
Configuración
department_namestringOnly fire for postings in the department with this exact name, e.g. `Engineering`. Matched exactly and case-sensitively; use `ASHBY_LIST_DEPARTMENTS` to find your department names. Leave unset to fire for every department.
Payload del evento
jobPostingobjectObligatorioThe posting as it stands after being taken down. `isListed` is false by definition here.
Job Posting UpdatedASHBY_JOB_POSTING_UPDATEDTriggerTriggers when anything on a job posting changes — its title, department, locations, compensation or deadline. Also fires alongside a publish and an unpublish, so enabling those triggers too gives two deliveries per action.
ASHBY_JOB_POSTING_UPDATEDTriggerTriggers when anything on a job posting changes — its title, department, locations, compensation or deadline. Also fires alongside a publish and an unpublish, so enabling those triggers too gives two deliveries per action.
Configuración
department_namestringOnly fire for postings in the department with this exact name, e.g. `Engineering`. Matched exactly and case-sensitively; use `ASHBY_LIST_DEPARTMENTS` to find your department names. Leave unset to fire for every department.
Payload del evento
jobPostingobjectObligatorioThe posting after the change. Ashby sends no before/after diff, so which field changed is not stated.
Job UpdatedASHBY_JOB_UPDATEDTriggerTriggers when a job — the internal requisition, not its public posting — changes, including when it opens, closes, or moves to a different interview plan. Confidential jobs are never delivered.
ASHBY_JOB_UPDATEDTriggerTriggers when a job — the internal requisition, not its public posting — changes, including when it opens, closes, or moves to a different interview plan. Confidential jobs are never delivered.
Configuración
job_statusstringenumOnly fire when the job's status after the change is this one. This is the resulting status, not a transition, so an already-closed job that is edited again fires again with `Closed`. Leave unset to fire for every status.
DraftOpenClosedArchived
Payload del evento
jobobjectObligatorioThe job after the change. Ashby sends no before/after diff, so which field changed is not stated.
Offer CreatedASHBY_OFFER_CREATEDTriggerTriggers when an offer process is started for a candidate. Later changes to that offer — new versions, approvals, the candidate's response — fire the offer-updated trigger instead.
ASHBY_OFFER_CREATEDTriggerTriggers when an offer process is started for a candidate. Later changes to that offer — new versions, approvals, the candidate's response — fire the offer-updated trigger instead.
Configuración
Sin parámetros.
Payload del evento
offerobjectObligatorioThe offer, with its first version and the offer form's shape.
Offer DeletedASHBY_OFFER_DELETEDTriggerTriggers when an offer process is deleted. This is the only way to observe the deletion — a deleted offer no longer appears in any Ashby list endpoint.
ASHBY_OFFER_DELETEDTriggerTriggers when an offer process is deleted. This is the only way to observe the deletion — a deleted offer no longer appears in any Ashby list endpoint.
Configuración
Sin parámetros.
Payload del evento
offerobjectObligatorioThe deleted offer, by id. Nothing else survives the deletion, so the id no longer resolves against Ashby.
Offer Signature Request UpdatedASHBY_OFFER_SIGNATURE_REQUEST_UPDATEDTriggerTriggers when an e-signature request on an offer letter is sent, cancelled, completed or deleted. Signature requests attached to an application — an NDA, a consent form — are a separate trigger, because Ashby gives the two different fields.
ASHBY_OFFER_SIGNATURE_REQUEST_UPDATEDTriggerTriggers when an e-signature request on an offer letter is sent, cancelled, completed or deleted. Signature requests attached to an application — an NDA, a consent form — are a separate trigger, because Ashby gives the two different fields.
Configuración
event_typestringenumOnly fire on this point in the signature request's life. Ashby delivers one event per point, so leaving this unset means four deliveries per request; `completed` means the document came back signed.
sentcancelledcompleteddeleted
Payload del evento
eventTypestringenumWhat happened to the signature request. `completed` means the document came back signed.
sentcancelledcompleteddeletedofferIdstringObligatorioId of the offer the document belongs to.
offerVersionIdstringId of the offer version the document was generated from.
Offer UpdatedASHBY_OFFER_UPDATEDTriggerTriggers when an offer changes — a new version is drafted, it moves through the approval chain, or the candidate accepts or declines. Creation of the offer fires the offer-created trigger instead.
ASHBY_OFFER_UPDATEDTriggerTriggers when an offer changes — a new version is drafted, it moves through the approval chain, or the candidate accepts or declines. Creation of the offer fires the offer-created trigger instead.
Configuración
Sin parámetros.
Payload del evento
offerobjectObligatorioThe offer after the change. `acceptanceStatus` and `offerStatus` carry where it now stands; Ashby sends no before/after diff.
Opening CreatedASHBY_OPENING_CREATEDTriggerTriggers when an opening — Ashby's headcount record, which jobs hire against — is created. Ashby publishes no update or delete event for openings, so this is the only opening event available.
ASHBY_OPENING_CREATEDTriggerTriggers when an opening — Ashby's headcount record, which jobs hire against — is created. Ashby publishes no update or delete event for openings, so this is the only opening event available.
Configuración
Sin parámetros.
Payload del evento
openingobjectObligatorioThe opening, with its current details under `latestVersion` — including the jobs hiring against it.
Survey SubmittedASHBY_SURVEY_SUBMITTEDTriggerTriggers when a candidate submits a survey. Ashby never includes the answers for Diversity and EEOC surveys, anonymous or not, and does not fire at all for an anonymous Candidate Experience submission.
ASHBY_SURVEY_SUBMITTEDTriggerTriggers when a candidate submits a survey. Ashby never includes the answers for Diversity and EEOC surveys, anonymous or not, and does not fire at all for an anonymous Candidate Experience submission.
Configuración
survey_typestringenumOnly fire for this kind of survey. The five kinds drive different workflows — a questionnaire feeds the scorecard, a consent form gates data processing, a candidate-experience survey feeds NPS. Leave unset to fire for every kind.
CandidateDataConsentCandidateExperienceDiversityEEOCQuestionnaire
Payload del evento
surveySubmissionobjectObligatorioThe submission, with the form's shape alongside the answers so each key in `submittedValues` can be resolved to its question.
Take-Home Assignment AssignedASHBY_TAKE_HOME_ASSIGNMENT_ASSIGNEDTriggerTriggers when a take-home assignment is issued to a candidate and enters Waiting On Submission. The candidate has not submitted anything yet.
ASHBY_TAKE_HOME_ASSIGNMENT_ASSIGNEDTriggerTriggers when a take-home assignment is issued to a candidate and enters Waiting On Submission. The candidate has not submitted anything yet.
Configuración
Sin parámetros.
Payload del evento
takeHomeAssignmentobjectObligatorioThe take-home assignment, with its assigned reviewers. `submission` is null until the candidate hands work in.
Take-Home Assignment CancelledASHBY_TAKE_HOME_ASSIGNMENT_CANCELLEDTriggerTriggers when a take-home assignment is cancelled, whether or not the candidate had already submitted.
ASHBY_TAKE_HOME_ASSIGNMENT_CANCELLEDTriggerTriggers when a take-home assignment is cancelled, whether or not the candidate had already submitted.
Configuración
Sin parámetros.
Payload del evento
takeHomeAssignmentobjectObligatorioThe take-home assignment as it stood when it was cancelled. `submission` is present only if the candidate had already handed work in.
Take-Home Assignment CompletedASHBY_TAKE_HOME_ASSIGNMENT_COMPLETEDTriggerTriggers when a take-home assignment reaches Complete, which happens once reviewers finish rather than when the candidate submits.
ASHBY_TAKE_HOME_ASSIGNMENT_COMPLETEDTriggerTriggers when a take-home assignment reaches Complete, which happens once reviewers finish rather than when the candidate submits.
Configuración
Sin parámetros.
Payload del evento
takeHomeAssignmentobjectObligatorioThe take-home assignment, with the candidate's `submission` and each reviewer's feedback state.
Take-Home Assignment SubmittedASHBY_TAKE_HOME_ASSIGNMENT_SUBMITTEDTriggerTriggers when a candidate submits their take-home and it enters Waiting On Feedback. Review has not happened yet — that fires the take-home-assignment-completed trigger.
ASHBY_TAKE_HOME_ASSIGNMENT_SUBMITTEDTriggerTriggers when a candidate submits their take-home and it enters Waiting On Feedback. Review has not happened yet — that fires the take-home-assignment-completed trigger.
Configuración
Sin parámetros.
Payload del evento
takeHomeAssignmentobjectObligatorioThe take-home assignment, with the candidate's `submission` and the reviewers it is waiting on.