--- title: "Connect Teamtailor to Metaintro | Metaintro" canonical: "https://www.metaintro.com/help/connect-teamtailor-to-metaintro" language: "en" author: "Metaintro" published: "2026-11-11T16:02:32.110Z" modified: "2026-11-11T16:02:45.836Z" --- # Connect Teamtailor to Metaintro Create a Teamtailor API key and webhook so people who share with you arrive in Teamtailor and their stages flow back to Metaintro. Last updated: November 11, 2026[Employers](/help/category/employers) Paste it into Claude, ChatGPT, Codex, Cursor or Pi. ## Before you start You need Company Admin access in Teamtailor. To get stage updates quickly, the Webhooks add-on must also be switched on. A Company Admin turns it on in Teamtailor's Add-on feature center. You will paste three things into Metaintro: - Your Teamtailor data region: eu, na or au. - An API key with the Admin scope and Read/Write permissions. - The email address of a Teamtailor user. Metaintro posts its notes as this user. ## Create the credential in Teamtailor First, find your data region. In Teamtailor, go to Settings → Company → General → Data processing. The region is at the bottom of the page. Europe (Ireland) is eu, North America (Oregon) is na, and Asia-Pacific (Australia) is au. See [Different regions for data processing](https://support.teamtailor.com/en/articles/8031426-different-regions-for-data-processing). Then create the API key. These steps follow Teamtailor's guide, [Use our Teamtailor API](https://support.teamtailor.com/en/articles/5963369-use-our-teamtailor-api). 1. In Teamtailor, go to Settings → Integrations → API keys. 2. Select + New API Key in the top-right corner. 3. Give the key a name, such as Metaintro. You can add a description. 4. Leave the expiry date empty, or pick a date. When the key expires, Metaintro stops working until you connect again with a new key. 5. Set API scope to Admin. Only Admin keys can read and create candidates. 6. Set Permissions to Read/Write. 7. Save the key. Then select Copy to copy it. You cannot change a key's scope or permissions after you create it. If you picked the wrong ones, create a new key. ## Connect in Metaintro 1. In Metaintro, go to Settings > Integrations and choose Teamtailor. 2. In Data region, enter eu, na or au. 3. In API key, paste the key you copied. 4. In Note author email, enter the email of an existing Teamtailor user. Metaintro posts its notes as this user. 5. Select Connect. Metaintro checks the key and looks up that user. After you connect, Metaintro shows a Webhook address. Set up the webhook in Teamtailor so stage changes reach Metaintro quickly. These steps follow Teamtailor's [Company Webhooks](https://support.teamtailor.com/en/articles/8068954-company-webhooks) guide. 1. In Teamtailor, go to Settings → Integrations → Webhooks. 2. Select Add webhook (some accounts show New Webhook). 3. Enter a label, such as Metaintro. 4. Paste the Webhook address from Metaintro as the webhook URL. 5. Choose the job application events, including the job application update event. It fires when a candidate changes stage or is rejected. 6. If Teamtailor asks for a signature version, choose version 2. Metaintro does not accept the older version 1. 7. Select Save. Teamtailor then shows the webhook's signature key. 8. Copy the signature key. In Metaintro, paste it into Signing token and select Save token. Then map your jobs, set your rules, preview, and go live. ## What Metaintro sends and reads Metaintro only sends people who chose to share their profile with you for a job. For each person, Metaintro: - Finds the candidate by exact email. If there is no match, it creates a new candidate marked as sourced. - Adds the candidate to the job you mapped, as a sourced application. - Uploads their résumé when they have one. - Adds a comment with a link to their proof card. The comment is posted as your note author. Metaintro also reads your jobs so you can map them. It can move an application to a stage whose name matches, such as an interview stage. Stage updates come back by webhook. Metaintro also re-checks stages on a regular schedule, in case a webhook is missed. Metaintro reads the current stage, whether the candidate was hired, and whether they were rejected or withdrew. ## Limits - Teamtailor allows 50 API requests every 10 seconds. Metaintro stays under this limit and waits when Teamtailor asks it to. - Teamtailor does not retry failed webhooks. Metaintro's regular re-check picks up any changes a missed webhook would have sent. - Metaintro can only move an application to a stage when the job has a stage with a matching name. It does not move applications that were already rejected or withdrawn. - If a person has no email address, Metaintro cannot match them to an existing candidate. ## If something goes wrong - The key is rejected: the key may be wrong, expired, or deleted. Create a new key and connect again. - Metaintro cannot read candidates or jobs: the key needs the Admin scope with Read/Write permissions. You cannot change an existing key's scope, so create a new key. - The note author is not found: enter the email of an active Teamtailor user, exactly as it appears in Teamtailor. - The connection fails right away: check the data region. A key from a North America account only works with na, and an Asia-Pacific key only works with au. - Stage updates are slow: check that the webhook uses the Webhook address from Metaintro, uses signature version 2, and has the same signature key you saved in Metaintro. - Too many requests: Metaintro pauses and tries again later. You do not need to do anything. ### 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)