Ashby + DodoForm
Create Ashby candidates from verified DodoForm records. Resumes, emails and voice notes become structured candidate data with a human review step before the ATS.
What happens on each record
A candidate is created in Ashby from the verified record, via the `candidate.create` endpoint.
The push runs after a record is approved — by the confidence gate or by a human in the review queue — so Ashby only ever receives data that has been checked. That ordering is the point: AI-extracted values that nobody verified are worse than no values, because they are indistinguishable from real ones once they land.
What you need to connect it
An Ashby API key, sent as HTTP Basic auth. Stable, with no expiry to manage.
Before you turn it on
- Requires the Max plan or above.
- The request contract was verified against Ashby's official documentation: `candidate.create` is a POST with Basic auth and a required `name`, and Ashby's `success: false` response envelope is handled explicitly rather than being mistaken for an HTTP failure.
- Currently Beta: what is missing is one round-trip with a real Ashby key, which cannot be exercised without an account.
Who this is for
Recruiters on Ashby whose candidates arrive as resumes and forwarded emails, where the retyping is the actual work.