Before you start
Your Recruit CRM account must be on the Business plan or higher. Free trials can't use the API.
Only the Account Owner can turn on and copy the API token. An admin who isn't the Account Owner can ask the owner for a custom role with access to the API token.
You will paste one thing into Metaintro: your Recruit CRM API token.
Create the credential in Recruit CRM
Sign in to Recruit CRM as the Account Owner.
Go to Admin Settings.
Scroll down and select API to open the API section.
Turn the toggle on to enable the API token.
Copy the token.
Recruit CRM's guide: Recruit CRM API documentation.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose Recruit CRM.
In API token, paste the token you copied.
Select Connect.
Metaintro checks the token by reading your Recruit CRM user list. Then map your Recruit CRM jobs to your Metaintro 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 that job. For each person, Metaintro:
Looks for a Recruit CRM candidate with exactly the same email. If there is one, Metaintro uses that candidate. If there is none, it creates a candidate with their name, email and phone when they shared them, their résumé when they shared one, and the source set to Metaintro.
Assigns the candidate to the job, unless they are already assigned to it.
Adds a note on the candidate, linked to the job, with a link to their proof card, plus their short summary when they wrote one.
Metaintro checks each shared candidate's hiring stage on the job regularly. It reads the stage name, so stages named like Placed or Rejected show up in Metaintro as hired or not selected. When you move a candidate from Metaintro, it picks the stage in the job's hiring pipeline whose name matches.
Limits
Stage updates are not instant. Recruit CRM documents no way to check that a webhook really came from Recruit CRM, so Metaintro checks for changes on a schedule.
Metaintro sends the résumé only when it creates the candidate. If the person is already in Recruit CRM, Metaintro leaves their existing résumé alone.
If more than one candidate has the person's email, Metaintro doesn't guess. It stops and doesn't send that person.
A person who shared no email can't be matched, so Metaintro creates a new candidate for them.
Metaintro reads stage names. If you renamed or added stages, a name it doesn't recognize shows as still in progress, and a move from Metaintro may find no matching stage.
Recruit CRM allows at least 60 API requests a minute for each token. Metaintro stays under that, so many shares at once can take a few minutes.
If something goes wrong
Token rejected. Check that you pasted the whole token and that the API toggle is still on in Admin Settings. If the Account Owner turned it off or the token changed, copy it again and reconnect.
Plan or permission error. Recruit CRM refuses API access below the Business plan. Upgrade the plan, or ask the Account Owner to check API access.
Rate limited. Metaintro pauses and retries on its own. No action is needed.
A candidate didn't arrive. Check that the Recruit CRM job is still mapped in Metaintro, and that no other candidate shares the person's email.