Before you start
A Lever Super Admin needs to approve Metaintro. Lever only lets Super Admins authorize integration apps for the whole company, and only Super Admins can set up webhooks. Lever's guide: OAuth for Lever integrations.
In Metaintro, you need to be someone who can manage your team in your employer account. If Settings > Integrations says ATS sync isn't on for your account yet, ask your Metaintro contact.
You don't paste a key to connect. Instead:
Use the same email address in Lever and Metaintro. Metaintro finds your Lever user by the email you sign in to Metaintro with, and that Lever user must be active.
Finish the approval in the same browser session you started it from. Lever sends you back to Metaintro, and Metaintro checks it is still you.
After connecting, you'll paste one value from Lever: the webhook signing token, so stage changes reach Metaintro quickly.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose Lever.
Select Continue to Lever. Metaintro sends you to Lever's sign-in and approval page.
Approve Metaintro in Lever
Sign in to Lever as a Super Admin if Lever asks.
Lever lists the permissions Metaintro is asking for. In plain English, Metaintro asks to:
View and manage candidates and their opportunities, so it can add people to a job, add their proof card link, and move them between stages.
View your job postings, so you can map them to your Metaintro jobs.
View and manage notes, so it can add a note with each person's proof card.
View and manage files, so it can attach a résumé.
View your pipeline stages and archive reasons, so it can tell where someone is and whether they were hired.
View your users, so it can find your Lever user.
Stay connected, so you don't need to approve again every hour.
Accept the request.
Lever sends you back to Metaintro, which shows "Lever is connected."
Metaintro then appears in your Lever settings as an authorized app. A Super Admin can revoke its access there at any time.
Turn on stage updates in Lever
After connecting, Metaintro shows a webhook address and a Signing token field.
In Lever, go to Settings > Integrations and API, then open the Webhooks tab. You must be a Super Admin.
Turn on Candidate Stage Change and paste Metaintro's webhook address as its URL.
Do the same for Candidate Archive State Change and Candidate Hired, using the same address.
Make sure Lever has a signing token for webhooks. Lever only signs webhooks once a signing token exists, and Metaintro ignores unsigned ones. Copy the signing token.
In Metaintro, paste it into Signing token and select Save token.
If you regenerate the signing token in Lever later, paste the new one into Metaintro too. Lever's guide: Webhooks in the Lever API documentation.
Finally, map your Lever postings 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 details with you for a job. For each person, Metaintro:
Looks for an existing opportunity with the same email address on the Lever posting you mapped. If it finds exactly one, it uses that. If it finds more than one, it stops and does not guess.
Otherwise creates an opportunity on that posting with their name, email, phone and a link to their proof card. The origin is Applied and the source is Metaintro. If Lever already has a candidate with that email, Lever adds the new opportunity to that candidate.
Attaches their résumé as a file on the opportunity when they shared one.
Adds a note with a link to their proof card and any summary they shared.
New opportunities, notes and files are recorded as the Lever user who connected Metaintro, and that user owns the new opportunities.
Metaintro reads your postings so you can map them, and reads each person's current stage. When your webhook reports a change, Metaintro reads the opportunity again. If someone is archived with a hired reason, Metaintro marks them hired. If the archive reason says they withdrew, it marks them withdrawn. Any other archive reason counts as not selected. Metaintro also checks Lever on a schedule, so updates still arrive without the webhook, just more slowly.
When you move someone to Contacted, Interviewing or Offer in Metaintro, Metaintro moves their Lever opportunity to the first Lever stage whose name matches.
Limits
Lever allows about 10 requests a second for each connection, with short bursts up to 20. Metaintro paces its requests and waits when Lever asks it to slow down.
Metaintro never hires, rejects or archives anyone in Lever. Do that in Lever.
Stage moves only work when your Lever pipeline has a stage whose name matches, such as a screen or interview stage, or Offer.
Confidential postings and confidential candidates are not visible to Metaintro, so you can't map confidential postings.
The résumé is added to the opportunity's files. Lever does not parse it into the candidate's profile.
Metaintro finds existing opportunities by email only. Someone who shared without an email always gets a new opportunity.
If Metaintro doesn't use the connection for 90 days, Lever ends its access and you need to connect again.
Metaintro connects to one ATS at a time.
If something goes wrong
"We couldn't finish connecting Lever": check that you approved as a Super Admin, that your Lever user is active, and that its email matches the email you sign in to Metaintro with. Then start again from Settings > Integrations. If you cancelled on Lever's page, start again too.
Missing permission: if Lever refuses a request, a Super Admin should disconnect Lever in Metaintro, connect again, and accept every permission Lever lists.
Access revoked or expired: if Settings > Integrations says the last sync failed, disconnect Lever and connect again. If people were already sent through the old connection, ask your Metaintro contact to help you reconnect.
Rate limited: Metaintro waits and tries again. No action is needed unless it keeps happening.
Stage changes are slow to arrive: in Lever's Webhooks tab, check that Candidate Stage Change, Candidate Archive State Change and Candidate Hired are on and point to Metaintro's webhook address. Make sure the signing token saved in Metaintro is the current one in Lever.
A person was not sent: if more than one Lever opportunity on that posting has their email, Metaintro does not choose between them. Merge or archive the duplicates in Lever and share again.