Connect Pinpoint to Metaintro

Before you start

You need a Pinpoint user who can open Settings and the API & Webhooks page. Pinpoint's guide does not name a specific role or plan for this, so if you can't see that page, ask a Pinpoint admin.

You will paste two things into Metaintro:

Your Pinpoint subdomain. This is the part before .pinpointhq.com in the address you use to sign in. For acme.pinpointhq.com, it is acme.
A Pinpoint API key.

Create the credential in Pinpoint

These steps follow Pinpoint's guide, Managing and monitoring your Pinpoint API.

Sign in to Pinpoint and select Settings in the left sidebar.
Select API & Webhooks.
Make sure the Pinpoint API toggle in the top-right corner is switched on.
Open the API Keys tab and select + Create new.
Name the key, for example "Metaintro".
Set its permissions. Metaintro reads your jobs and stages, and adds applications and comments, so it needs Write and Delete access. Assign all grants this in one step.
Select Create API key and copy the key.

Connect in Metaintro

In Metaintro, go to Settings > Integrations.
Choose Pinpoint.
In Account subdomain, enter your subdomain (for example acme).
In API key, paste the key you just created.
Select Connect.

Then map your Metaintro jobs to Pinpoint 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. For each person, Metaintro:

Creates an application on the Pinpoint job you mapped. Pinpoint creates the candidate with it. The source shows as Job Board, with Metaintro as the source detail.
Attaches their résumé to the application when they shared one.
Adds a comment with a link to their proof card and a short summary.
Reuses a candidate who is already in Pinpoint with the same email address, instead of creating a second one.

Metaintro reads your Pinpoint jobs so you can map them. It checks each shared candidate's stage regularly, so a move in Pinpoint shows up in Metaintro after a short delay. When you move a candidate in Metaintro, it moves their Pinpoint application to the matching stage, if your job has one.

Limits

Pinpoint needs an email address to create an application. People who shared only a phone number can't be sent to Pinpoint.
Pinpoint accepts résumés as PDF or Word files only. A résumé in another format stops that delivery.
Pinpoint can't add a résumé to an application that already exists. If someone who shared a résumé is already on that job in Pinpoint, the delivery stops.
Stage updates are checked regularly, not sent instantly. Pinpoint's webhooks have no documented way to prove they came from Pinpoint, so Metaintro doesn't use them.
Pinpoint doesn't publish a rate limit. If it asks Metaintro to slow down, Metaintro waits and tries again.

If something goes wrong

The key is rejected. Check that you copied the whole key with no extra spaces, that the key still exists under API Keys, and that the Pinpoint API toggle is on. Then connect again.
Missing permission. Edit the key under API Keys and give it Write and Delete access, or select Assign all.
Wrong subdomain. Enter only the part before .pinpointhq.com, with no https:// and no slashes.
Too many requests. Metaintro waits and retries on its own. You don't need to do anything.
A candidate didn't arrive. Check that they shared an email address and, if they shared a résumé, that it is a PDF or Word file. Pinpoint's API Logs tab, on the same API & Webhooks page, lists every request Metaintro made.