Integrations
How to connect each outside tool (calendars, the Zoom, Meet and Teams note taker, Granola, Claude, job boards, an ATS), who sets it up, the exact steps, and what you see when it is not set up yet.
Before you start
Every integration is optional. Leaving one unconnected is a supported way to run the product: scheduling falls back to availability rules, a round held elsewhere is filed by pasting its transcript, and nothing stops working.
Most connections are made in Settings, in the sidebar. Settings has six tabs: General, Hiring, Offers, Interviews, Scheduling and Integrations. Each section below says which tab to open.
Who sets each one up:
| Integration | Who connects it | |---|---| | Google Calendar or Microsoft 365 | each interviewer, for their own calendar | | The join link for interviews | an owner or admin, once for the company | | The note taker on Zoom, Meet and Teams | nobody connects anything; each interviewer agrees once | | Granola | each interviewer, with their own Granola key | | Claude, or another MCP client | each person, from their own assistant | | Job boards and Google | nothing to connect; publishing does it | | An applicant tracking system | an owner or admin, once it is available |
Some integrations also need setting up on our side. Until that has happened, Settings shows the integration as not available yet, or hides it, and never offers a button that cannot work. The steps below say what that looks like.
Calendars: Google Calendar and Microsoft 365
Connecting your calendar does two things. The times a candidate is offered leave out anything marked busy on it, and a human round you lead is put on it with the rest of the panel invited.
Who: each interviewer connects their own. Nobody can connect a calendar for someone else.
- Open Settings → Scheduling and find Calendar.
- Click Connect Google Calendar or Connect Microsoft 365.
- Sign in to that account and accept every permission it asks for.
- You come back to Settings with "Your calendar is connected." The section then shows the account and a Disconnect button.
We read when you are busy, never what the meetings are. Events marked busy, out of office or tentative block a slot; events marked free do not. Busy times are cached for five minutes, and a candidate's chosen time is checked against your calendar again, live, when they confirm it.
What happens when a round is booked. A human round (live video, onsite, or on an outside call) goes on one calendar: the lead interviewer's, or if the lead has no calendar connected, the next person on the panel who does. Everyone else on the panel is an attendee on that one event. The candidate is never an attendee. They get a confirmation email with a calendar invite attached, sent from our address, so no interviewer's email address reaches them. A reschedule updates the same invite and a cancellation sends a cancellation for it. The AI screen is never put on a calendar.
If nobody on the panel has a calendar connected, no event is made, and the candidate still gets their confirmation and invite.
The join link. An owner or admin chooses, under Join link for interviews in the same section, which link every human round carries:
- Google Meet, created on the event when that event is on a Google calendar.
- Microsoft Teams, created on the event when that event is on a Microsoft 365 calendar.
- Each interviewer's own meeting link. Each person pastes their personal Zoom (or other) room under Your meeting link. A round uses the lead's, or another panellist's if the lead has not pasted one.
- No link. The candidate is told the team will send details. This is the default.
Everyone else sees the choice and cannot change it.
On the scheduling screen, each interviewer on the round is labelled "Calendar connected — busy times are left out" or "No calendar connected — availability rules only", so you can see whose calendar the offered times reflect.
When it is not set up. Only the providers that can be connected get a button. If neither can, the section says connecting a calendar is not available yet and points to your availability on the Team page. Google Meet and Microsoft Teams are offered as the join link only when their calendar can be connected; a saved choice that cannot be used is labelled "not available yet", with a note that interviews get no link until it is changed. If a connected calendar stops letting us in, the section says so and offers Reconnect. Until you reconnect, your times come from your availability rules only.
Limits.
- Personal Microsoft accounts cannot be connected. An outlook.com or hotmail.com account is refused with a message saying so; use a work or school account.
- Email is not connected. Candidate email always goes from our sending address, whichever calendar you connect.
- Disconnecting takes the interviews we put on your calendar off it and revokes our access.
- A round booked through Cal.com is already on the interviewer's calendar, so no second event is made. The candidate still gets our confirmation.
- A booking made by an API token or an assistant still goes on the calendar, because that reaches only staff. The candidate's confirmation waits in Inbox → Needs you for a person.
The note taker on Zoom, Google Meet and Microsoft Teams
When a human round's meeting link is a Zoom, Google Meet or Microsoft Teams link, a note taker joins the call, records the audio and transcribes it. The round is then scored like any other, against the job's criteria, with the candidate's own words as the evidence. There is nothing to install and no account to connect.
Who: each interviewer agrees once, for themselves.
- Open Settings → Interviews and find Note taker.
- Tick Let the note taker join my Zoom, Google Meet and Teams interviews.
Nobody can agree on someone else's behalf, admins included.
A round gets the note taker only when both of these are true:
- Every interviewer on the round has agreed. Until they have, the Note taker panel on the round's page says "Waiting for every interviewer to agree to the note taker in their settings" and names who has not.
- The candidate has been told the round is recorded. On the candidate's booking page the notice sits above the times, and they tick a box before they can book. If the round was booked another way, the round's panel has a Send the recording notice button, which emails the same notice.
There is no unrecorded version of a round. A candidate who needs an accommodation asks for one from the booking page, and a person decides; the request goes to the human-review queue with its usual deadline.
During the call. The note taker joins about two minutes early as a visible participant named after your company ("Acme Notetaker"). On Meet the notice is pinned in the chat, on Zoom it is sent to each person who joins, and on Teams it is posted in the chat. If it lands in a waiting room, admit it from the participant list. On Zoom, click Allow when asked to let it record. The round's panel tells you which of these it is waiting for.
The live co-pilot. The round's panel has Open the co-pilot. Keep that page open beside the call: it shows what has been said and suggests what to probe next.
Who said what. The transcript arrives with each voice already separated. The product places each voice as the candidate or an interviewer from the account, the email, an exact name match or who hosted the meeting. It never guesses. When a voice cannot be placed, the panel shows Say who is who. Name each voice and click Save and score the round. An interviewer named once on Zoom or Teams is recognised on later calls; Meet does not give a stable id, so Meet voices are named each time when they cannot be placed.
When it is not set up. If the note taker is not available on your account, Settings does not show the note-taker agreement at all, the booking page shows no recording notice, and a round held on Zoom, Meet or Teams says to paste the transcript after the call.
Limits.
- Audio only, never video. The audio is deleted after 30 days. The transcript is kept like the rest of the application.
- Only Zoom, Google Meet and Microsoft Teams links. A Webex or Cal.com video link, or any other link, leaves the round as it was, and its transcript is pasted.
- A round booked less than about twelve minutes ahead may start before the note taker arrives, and one the waiting room never admits cannot be recorded. In both cases the panel asks for a pasted transcript instead.
- One transcript per round. If a transcript was already filed by hand, the note taker's copy is not used.
Granola
If you take interview notes in Granola, you can file a human round's transcript from one of your notes instead of pasting it.
Who: each interviewer connects their own Granola. The key reads only that person's notes.
- In the Granola app, open Settings, then Connectors, then API keys, and create a key with access to your personal notes. API keys need a Granola Business or Enterprise plan.
- In Briefing Room, open Settings → Interviews and find Granola.
- Paste the key into Granola API key and click Connect Granola. The key is checked with Granola before it is saved, and it is never shown again.
Importing a round.
- On the candidate's page, open Paste Transcript for the round.
- Choose Import from Granola. It lists your notes from the day either side of the round's time (a week, if the round has no time), best match first.
- Pick the note. For a one-to-one round recorded on your own Granola, the voices are placed automatically. Otherwise say which voice is the candidate.
- If the candidate was not already told by the product that the round was recorded, tick The candidate was told this call was being recorded and transcribed. Your confirmation is kept with the transcript.
- Click Import and score.
The import goes through the same scoring as every other round, and we only read your notes, never change them.
Limits.
- Human rounds only. An AI screen has its own transcript.
- Write-once. Importing the same note again changes nothing; a round that already has a transcript refuses a different one.
- A note Granola has not finished summarising cannot be imported yet.
- If Granola stops accepting your key, the section says so and asks for a new one.
- An API token for the whole company (a service account) has no Granola of its own. Use a person's token.
Claude and other AI assistants (MCP)
You can connect Claude, or any assistant that speaks MCP with OAuth sign-in, to your hiring pipeline. The assistant can then read candidates with the quotes behind every score, move people through a job, book interviews and draft emails.
Who: each person connects their own assistant. It acts as them, in the company they are signed in to, with exactly the access they already have.
- In Claude, add a custom connector with the address shown under Settings → Integrations → API tokens, in Connect Claude. Until that box shows an address, connecting this way is not available yet.
- Claude opens our Connect an assistant page. Sign in if you are not already.
- Check the Signed in as and Organization lines and click Continue.
- Approve the consent screen that names the assistant, and you are back in Claude.
Disconnect from the assistant's own connector settings at any time.
What it may do. Owners and admins get admin access through the assistant; everyone else gets the access their role allows. Its permissions follow your role as it is at each call, so a change of role applies at once, and a deactivated member's assistant stops working on its next call.
Anything that would reach a candidate waits for a person. An email the assistant drafts, a rejection with an email, or an invite it would trigger waits in Inbox → Needs you instead of being sent (see below).
Developers can instead run the server locally with a personal token from Settings → Integrations → API tokens.
Job boards and Google
There is nothing to connect. Publishing a role lists it on your careers page, in Google's job search, in the sitemap, and in the XML feeds for Jooble, Talent.com and Adzuna. Only verified companies' roles appear in the sitemap and the feeds.
On the job's page, the Listing panel shows whether the role is Live, Private or Expired, and has Renew for 30 days and Keep this role private. It also has ready-to-paste text for LinkedIn, Wellfound and Hacker News, each carrying a tagged link, and counts applicants by the channel they came from. Owners, admins and recruiters can renew a listing or make it private.
The listing clock, what expiry does, and privacy are described in Publishing a role.
Applicant tracking systems: Ashby, Lever and Greenhouse
Not available yet. Connections to Ashby, Lever and Greenhouse are built, and switched off until each has been tested against a real account. Until then Settings shows no Applicant tracking system section, except to a company that already stored a key, so it can disconnect.
How the connection works once a vendor is switched on (a signed webhook, applicants held rather than guessed, nothing written back) is in ATS integrations.
Adding résumés in bulk
To put people who did not apply through the careers page into a role, open the job and click Add résumés in its header. An active job takes uploads, and so does a draft once its rubric exists, so you can bring candidates in before the job is public. A draft with no rubric says to generate it first, a draft with neither an advance nor a reject score says to set them, and a paused or closed job says to resume it. Your company has to be verified (and not paused by us), because every upload emails the person in its name.
Drop CVs, a folder of them, or a zip: PDF, Word, text or images, up to 500 in one batch, and a zip may hold up to 500 more. The page shows no cost estimate (D-200). Files are read about 20 a minute. Each file then shows its progress: Added, Already on this job (linked to the existing candidacy, never merged), Needs an email address (add it on the page, or on the candidate's own page later), or Couldn't read it. Someone already in your candidates is added with the résumé on file, and the row says the new file was not used. A CV with no email address uploaded twice is linked to the first when its text is the same. When the batch is done the page links to the job and to Inbox.
Each person added is scored against the job's rubric and emailed a notice that an AI tool will compare their CV with the role. They never applied, so nothing rejects them automatically, and nothing advances them after a round: those decisions wait in Inbox → Needs you for a person. Once your AI notice period has passed, one who clears the job's advance number can still be invited to the AI screen, which asks for their consent to recording, and the notice email says so. Owners, admins, recruiters and the job's creator can upload.
If uploads are not available on your account, the page says so.
Ask AI
Press Cmd+K on a Mac, or Ctrl+K elsewhere, from any page of the company side of the app, or click the assistant icon. The same keys close it. Ask about candidates, jobs and the pipeline in plain language. The answer covers only the jobs you can see and says so.
A quote in an answer is checked against the real transcript before you see it, and one that is not there is struck out. When the answer suggests an action, such as drafting an email or starting a round, it is a button, and nothing happens until you press it. Anything candidate-facing then waits in Inbox → Needs you.
Inbox → Needs you
Needs you, the first view of the Inbox in the sidebar, is the one list of everything waiting on a person before it reaches a candidate. The Inbox's count in the sidebar includes it.
- decisions the scores would make while automatic decisions are off, with the scoring model's recommendation (see Deciding);
- emails and rejections that an API token, an MCP client or Ask AI drafted;
- interview confirmations for bookings an API token made;
- candidacies held because a token started the work, because the candidate was added by your team rather than applying, or because your AI notice has been live for under ten business days.
Approve and send sends exactly what the list showed, and an email can be edited first with Edit. Reject runs nothing. A held candidacy has its own buttons, such as Start the round, Advance to the next stage once a round has happened, or Reject, which asks why and whether to email them. Holds you fix elsewhere (no rubric, no AI screen stage, nobody assigned to a round, an expired consent link, no email address) link to where the fix is made, and a candidate's request for a person can be closed with a written answer.
Everything is re-checked when you approve: that you still have authority over the job, that the candidacy is still open, and that the candidate has not been erased or asked not to be contacted. If anything has changed, nothing is sent and the item says why. Only a signed-in person can approve; a token cannot approve its own draft. A drafted action that nobody decides within seven days expires.