How to configure the Ashby integration with Get on Board

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.

Connect Ashby in Get on Board

1. Open the user menu in Get on Board and go to Integrations.
2. Choose Ashby as your ATS provider.
3. In Ashby, generate an API key under Settings > API for your workspace.
4. Make sure that key includes jobsRead, candidatesWrite, and apiKeysWrite.
5. Copy the API key into Get on Board.
6. 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.
7. Click Save and import.
8. Wait for Get on Board to confirm the connection and register the webhook in Ashby.
9. 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.

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

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 custom fields or survey answers that Get on Board does not send in the current integration.

Related articles

• What is Ashby and what can I do with the Ashby integration?
• Integrate Get on Board with your external ATS (Lever, Greenhouse, Ashby)
• What data is sent to my external ATS when using the Get on Board integration?
• Why did I receive an ATS integration disabled email?