Ashby: Sync application ArchiveDetail custom field values
AnsweredWhich connector?: Ashby
Additional details:
The Ashby connector syncs ArchiveDetail custom field definitions into custom_field and coarse archive fields on application (archive_reason_text, archive_reason_type). It does not sync the values selected when an application is archived.
Gap: For declined offers we can see a high-level reason (e.g. “Offer declined”) but not granular decline reasons (compensation, location, role fit, etc.) needed for recruiting analytics.
Expected: When an application is archived, sync ArchiveDetail custom field responses (including multi-select).
-
Official comment
Hi Vishal,
Thanks for the detailed inputs here.
Before we commit to an approach, we are verifying what Ashby's API exposes here. The field definitions are straightforward to retrieve, but we have not yet confirmed a supported way to read back the values chosen when an application is archived. We will be checking this and will get back if we hit any roadblocks.
Please sign in to leave a comment.
Comments
1 comment