Before you start
You need a BambooHR user who can open hiring settings. BambooHR runs every API call as the user who owns the key, so that user's access decides what Metaintro can see and do. Your BambooHR account must include Hiring (applicant tracking).
You will paste two things into Metaintro:
Your company subdomain. It is the part before .bamboohr.com in your BambooHR address. For example, if you sign in at acme.bamboohr.com, it is acme.
An API key.
We suggest creating the key as a dedicated hiring admin user, so the connection keeps working when staff change.
Create the credential in BambooHR
Sign in to BambooHR as the user who will own the key.
Select your name in the lower-left corner of any page to open your user menu.
Select API Keys. If you don't see it, your user doesn't have permission to create keys. Ask a BambooHR admin.
Select Add New Key, give it a name such as Metaintro, and generate it.
Copy the key now. BambooHR shows it only once.
BambooHR's guide: Getting started with the BambooHR API.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose BambooHR.
In Company subdomain, enter the part before .bamboohr.com.
In API key, paste the key you copied.
Select Connect.
Metaintro checks the key by reading your hiring statuses. Then map your BambooHR job openings 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:
Adds them as a candidate on the matching BambooHR job opening, with their name, email and phone when they shared them, and the source set to Metaintro.
Uploads their résumé when they shared one.
Adds their Metaintro proof card link as the candidate's website.
Adds a comment to the application with a link to their proof card, plus their short summary when they wrote one.
If a candidate with the same email already applied to that job, Metaintro adds its comment to that application instead of creating a new one.
BambooHR doesn't send hiring updates to other apps, so Metaintro checks each shared candidate's status regularly. It reads the status name, so statuses named like Hired or Not a Fit show up in Metaintro as hired or not selected. When you move a candidate from Metaintro, it picks the active BambooHR status whose name matches the stage.
Limits
Stage updates are not instant. Metaintro checks for changes on a schedule.
Metaintro reads status names. If you renamed or added statuses, a name it doesn't recognize shows as still in progress, and a move from Metaintro may find no matching status.
Metaintro matches an existing candidate by exact email on the same job. A person who shared no email can't be matched, so Metaintro creates a new application for them.
The key acts as the user who created it. If that user is deactivated or loses hiring access, the connection stops working.
BambooHR doesn't publish a request limit. If BambooHR slows Metaintro down, Metaintro waits and tries again.
If something goes wrong
Key rejected. Check the subdomain has no .bamboohr.com or https:// in it, and that you pasted the whole key. If the key was deleted, create a new one and connect again.
Missing permission. BambooHR returns this when the key's user can't open hiring settings or API access is turned off for your account. Give the user hiring access, or create the key as a hiring admin.
Blocked after several attempts. BambooHR blocks API access for a while after repeated tries with an unknown key. Wait, then connect with a correct key.
Rate limited. Metaintro pauses and retries on its own. No action is needed.
A candidate didn't arrive. Check that the BambooHR job opening is still open and mapped in Metaintro, and that the job's required application questions don't block new candidates added through the API.