Before you start
You need a TRAFFIT user who can open the integration settings.
The Integration API may be a paid add-on on your plan. If you cannot see Integration with the TRAFFIT API in Settings, ask your TRAFFIT account manager to turn it on.
You will paste three things into Metaintro: your TRAFFIT instance name, the API client name and its client secret.
Create the credential in TRAFFIT
These steps follow TRAFFIT's Integration API guide and API documentation.
In TRAFFIT, go to Settings > Integration with the TRAFFIT API.
Click +Add client.
Type a name using only letters and numbers, such as metaintro, and press Enter. TRAFFIT names the client in the form instance_name.
Leave Do you use API V1? off. Metaintro uses API V2.
Choose the employee and recruitment scopes.
Click Generate Client Secret.
Copy the full client name and the client secret from the summary.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose TRAFFIT.
In TRAFFIT instance name, enter the part before .traffit.com in your TRAFFIT address.
In API client name, paste the full client name, such as yourinstance_metaintro.
In Client secret, paste the secret.
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 TRAFFIT jobs so you can map them.
Candidate: Metaintro looks for an existing candidate with the same email address. If there is none, it creates one with their name and email, and the source Metaintro.
Résumé: uploaded to the candidate as a CV when the person has one.
Job: the candidate is added to the mapped job.
Note: a note on the candidate with the link to their proof card.
Metaintro checks each candidate's latest stage on the job regularly. A rejection stage reads as not selected, and stages named like hired or withdrawn are read that way. Metaintro can also move the candidate to the job stage whose name matches the step, or to a rejection stage.
Limits
TRAFFIT's webhooks are not signed, so Metaintro does not use them. Changes reach Metaintro on its next check, not right away.
TRAFFIT does not publish rate limits. Metaintro paces its requests.
Metaintro matches existing candidates by exact email only.
If something goes wrong
The client is rejected: check that you pasted the full client name, including your instance name, and the secret from the same client. Then connect again.
Access is refused: open the client in TRAFFIT and check it has the employee and recruitment scopes.
Too many requests: Metaintro waits and tries again by itself.
A stage cannot be set: your workflow has no stage with a matching name. Move the candidate in TRAFFIT.