--- title: "Connect Ashby to Metaintro | Metaintro" canonical: "https://www.metaintro.com/help/connect-ashby-to-metaintro" language: "en" author: "Metaintro" published: "2026-11-11T16:02:19.576Z" modified: "2026-11-11T16:02:37.160Z" --- # Connect Ashby to Metaintro Send candidates who chose to share with you straight into Ashby, with their résumé and proof card, and see their stage in Metaintro. Last updated: November 11, 2026[Employers](/help/category/employers) Paste it into Claude, ChatGPT, Codex, Cursor or Pi. ## Before you start You need an Ashby Organization Admin. Only Organization Admins can create API keys. API keys are available on Ashby's Foundations, Plus, Legacy Plus and Enterprise plans. You will paste one thing into Metaintro: an Ashby API key with these permissions: - Jobs: read - Candidates: read and write - Interviews: read - Hiring Process: read To have new candidates credited to Metaintro, add a source named Metaintro in Ashby first. If there isn't one, candidates arrive without a source. ## Create the credential in Ashby 1. In Ashby, go to Admin > Integrations > API Credentials. 2. Select + New to open the API key setup. 3. Name the key, for example Metaintro, choose the version, and select Create API Key. 4. Turn on the permissions listed above. A new key starts with no permissions. 5. Select Save and Continue, then copy the key. Ashby won't show it again after you close the setup. Ashby's guide: [How do I generate an API key?](https://docs.ashbyhq.com/how-do-i-generate-an-api-key) ## Connect in Metaintro 1. In Metaintro, go to Settings > Integrations. 2. Choose Ashby. 3. In API key, paste the key you copied. 4. Select Connect. Then map your Ashby jobs to your Metaintro jobs, set your rules, preview, and go live. ### Turn on stage updates After you connect, Metaintro shows a Webhook address and a Secret key. Copy both, then in Ashby: 1. Go to Admin > Integrations > Webhooks. 2. Select New. 3. Choose the event for candidate stage changes. This event also fires when someone is hired. 4. Paste the Webhook address as the URL and the Secret key as the secret token, then save. Metaintro shows the secret key only once. If you lose it, rotate it in Metaintro and paste the new one into Ashby. Ashby's guide: [Setting up webhooks](https://developers.ashbyhq.com/docs/setting-up-webhooks). ## What Metaintro sends and reads Metaintro only sends people who chose to share their profile with you for that job. For each person, Metaintro: - Creates the candidate in Ashby with their name, email and phone when they shared them, their Metaintro proof card link as their website, and your Metaintro source if you made one. - Creates an application on the matching Ashby job. - Uploads their résumé when they shared one. - Adds a note to the candidate with a link to their proof card, plus their short summary when they wrote one. If a candidate with the same email already exists, Metaintro uses that candidate and their application on that job instead of creating new ones. Metaintro reads each shared candidate's stage, including offers, hires and archiving. Archived candidates show as withdrawn when the archive reason says the candidate withdrew, and as not selected otherwise. The webhook tells Metaintro which candidates changed so it reads them first on its next sync. Without the webhook, Metaintro still checks every shared candidate on a schedule, which takes longer. When you move a candidate from Metaintro, it picks a stage in the candidate's interview plan: the Offer or Hired stage for those steps, and a stage whose name matches for earlier steps such as screening or interviews. To mark someone not selected or withdrawn, it archives them with an archive reason of the matching kind. ## Limits - Stage changes reach Metaintro on its next sync, not instantly. - Stage moves from Metaintro need a matching stage in the job's interview plan, and an active archive reason for rejections and withdrawals. - Metaintro matches an existing candidate by exact email. A person who shared no email can't be matched, so Metaintro creates a new candidate. - If two Ashby candidates share the same email, Metaintro stops and doesn't guess. - By default, Ashby keys can't see confidential jobs. Turn on access to confidential jobs and projects on the key if you want those jobs. ## If something goes wrong - **Key rejected.** Check you pasted the whole key and that it is still active in Admin > Integrations > API Credentials. If you lost it, create a new key. - **Missing permission.** Ashby rejects calls the key isn't allowed to make. Open the key in Ashby and turn on the permissions listed above. - **A confidential job is missing.** Turn on access to confidential jobs and projects on the key. - **Rate limited.** Metaintro pauses and retries on its own. No action is needed. - **Stage updates are slow.** Check the webhook in Ashby uses the current Webhook address and Secret key from Metaintro. If you rotated the key in Metaintro, paste the new one into Ashby. ### Was this article helpful? ## Related Articles - [Connect your ATS to MetaintroSend people who choose to share with you straight into your applicant tracking system, and see their stage in Metaintro.](/help/connect-your-ats-to-metaintro) [Return to navigation](#main-navigation)