Archive an Application with a Reason
A 6-step recipe with Ashby. We can help you get access.
Recipe · 6 steps
Archive an Application with a Reason
with Ashby · Talent Acquisition Management
Archive (reject) an application with a resolved archive reason.
- List the organization's archive reasons so the caller can pick a real reason id. Archived reasons are excluded so a retired reason is not used.
- Read the application to learn its job, which anchors the interview plan and therefore the archived stage lookup.
- Resolve the interview plan for the application's job.
- List the plan's stages so an archived stage can be identified. Match on the stage type field being Archived to obtain the archivedStageId.
- Move the application into the archived stage with the archive reason attached. Ashby requires archiveReasonId whenever the destination stage is of type Archived.
- Read the application back to confirm it is archived and that the reason and timestamp were recorded.
What you'll need to have ready
- applicationId: The id of the application to archive.
- archiveReasonId: The id of the archive reason to record. Resolve this from the listArchiveReasons step output.
- archivedStageId: The id of an interview stage whose type is Archived on the application's plan. Resolve this from the listPlanStages step output.
- archiveEmail: Whether Ashby should send the configured rejection email.
For your developer
Arazzo workflow ashby-hq:application-archive, 6 operations: archivereasonlist → applicationInfo → jobInterviewPlanInfo → interviewStageList → applicationChangeStage → applicationInfo. Specs on APIs.io.