When you want to use Get on Board as a company recruiter and keep your hiring process in Ashby, you configure the external ATS integration from Integrations with an Ashby API key.
Before you start
- You need a Recruiter or higher subscription plan with access to Integrations.
- If your subscription is paused, the integration settings stay disabled until the subscription resumes.
- You need an Ashby API key generated in your workspace under Settings > API.
- That API key should include jobsRead, candidatesWrite, and apiKeysWrite. Get on Board uses the same setup flow to read listed jobs, export candidates, and register the Ashby webhook that keeps connected jobs up to date.
- If your Ashby workspace restricts post-submit lookups, candidate or application read access may also be needed.
- Review the application form attached to the Ashby jobs you want to import. Get on Board can sync supported text, boolean, single-select, and multi-select questions, but unsupported required fields or mandatory surveys can still block candidate export.
Connect Ashby in Get on Board
- Open the user menu in Get on Board and go to Integrations.
- Choose Ashby as your ATS provider.
- In Ashby, generate an API key under Settings > API for your workspace.
- Make sure that key includes jobsRead, candidatesWrite, and apiKeysWrite.
- Copy the API key into Get on Board.
- Click Load boards and choose the Ashby job board you want to use. Leave All listed jobs selected only when Ashby already returns the listed jobs you need without a board filter.
- Click Save and import.
- Wait for Get on Board to confirm the connection and register the webhook in Ashby.
- Review the Ashby jobs found by Get on Board. From there, you can import a listed job as a draft or connect an existing Get on Board job to an Ashby posting. When the Ashby form includes supported application questions, Get on Board adds them to the candidate application flow for that connected job.
Choose how candidate export works
After the connection is active, open the integration settings and decide when candidates should be sent to Ashby:
- When they arrive in the Interested column
- When they arrive in the Applicants column
- Only when you send them manually
Prepare Ashby application questions
Get on Board treats supported Ashby application-form questions as Ashby-owned questions. Candidates answer them in Get on Board, and their answers are sent back to Ashby during export.
Use supported question types in Ashby when you need those answers to travel with the candidate:
- Text or long-text questions
- Boolean questions
- Single-select questions
- Multi-select questions
Keep sensitive, compliance, file-upload, survey, or other specialized required fields optional in Ashby unless your team has confirmed they are supported by the integration. If a required Ashby question cannot be represented safely in Get on Board, candidate export fails instead of sending an incomplete application.
If jobs or candidates do not sync as expected
- Confirm the API key is still active and has the permissions your team needs.
- If the connection saves but Ashby disables the webhook, confirm the same key still includes apiKeysWrite so Get on Board can keep that webhook enabled.
- Check that the Ashby jobs you want to import are listed in Ashby.
- If job import works but some candidate exports fail, review whether the Ashby application form requires unsupported fields, mandatory surveys, answers the candidate has not completed, or choices that changed in Ashby after the question was synced.
- If Quick Apply is no longer available for a connected job, check whether Ashby requires questions that need the full application flow.
More from Integrations and developer tools
