---
title: "Connect Crelate to Metaintro | Metaintro"
canonical: "https://www.metaintro.com/help/connect-crelate-to-metaintro"
language: "en"
author: "Metaintro"
published: "2026-11-11T16:02:22.336Z"
modified: "2026-11-11T16:02:39.307Z"
---

# Connect Crelate to Metaintro

Turn on Crelate API access and copy your API key so people who choose to share with you arrive in Crelate as contacts on your job pipelines.

Last updated: November 11, 2026[Employers](/help/category/employers)

Paste it into Claude, ChatGPT, Codex, Cursor or Pi.

## Before you start

You need Crelate's Business plan or higher. Admins always have API access. An admin can turn it on for other roles.

Metaintro acts as the user whose key you use, so use a user who can see your jobs and contacts.

You will paste one thing into Metaintro: a Crelate API key.

## Create the credential in Crelate

These steps follow Crelate's guide to [API key management](https://help.crelate.com/en/articles/4120534-api-key-management-and-documentation).

1. Sign in to Crelate.
2. Open **Your Profile & Preferences**.
3. Turn on **API Access**. Crelate creates the key for you.
4. Copy the API key.

## Connect in Metaintro

1. In Metaintro, go to **Settings > Integrations**.
2. Choose **Crelate**.
3. In **API key**, paste the key.
4. Select **Connect**.

Then map your jobs, set your rules, check the preview and go live.

## What Metaintro sends and reads

Metaintro only sends people who chose to share their profile with you for a specific job.

- **Jobs:** Metaintro reads your Crelate jobs so you can map them.
- **Contact:** Metaintro looks for an existing contact with the same email address. If there is none, it creates one with their name, personal email and mobile number. If you have a contact source named Metaintro, the contact uses it.
- **Pipeline:** the contact is added to the mapped job at the first stage of your recruiting workflow.
- **Résumé:** attached to the contact when the person has one.
- **Note:** a note on the contact, linked to the job, with the link to their proof card.

Metaintro checks each pipeline entry in Crelate regularly and reads its stage. A stage that means a positive outcome, such as Placed, reads as hired. A pass or negative outcome reads as not selected. Metaintro can also move the contact to the stage whose name matches the step.

## Limits

- Crelate allows about 120 requests a minute from one address, and may slow heavy use sooner. Metaintro paces itself below that.
- Crelate has no webhook for pipeline moves, so changes reach Metaintro on its next check, not right away.
- Metaintro matches existing contacts by exact email only.

## If something goes wrong

- **The key is rejected:** check that API Access is still on for that user, and copy the key again.
- **Access is refused:** the user behind the key cannot see that job or contact. Use a user with wider access, or ask an admin.
- **Too many requests:** Crelate's limit was reached. Metaintro waits and tries again by itself.
- **The candidate cannot be added to a job:** check that your recruiting workflow has an open first stage.

### 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)