Skip to content

AnswerReel Zapier integration: what it does and how to connect it

Pass candidates to your other apps when they submit, get scored or get a label, and send interview invites from those apps.

By The AnswerReel team. Updated .

The app is invite-only for now

You won't find AnswerReel by searching Zapier's app list yet. You add it to your Zapier account with an invite link instead. It's included on the Starter, Team and Agency plans, and the Owner of the organization finds the link in AnswerReel under Settings, then API and webhooks. If it isn't there, email support@answerreel.com and we'll send it.

What it can do

Three triggers start a Zap from AnswerReel, and one action lets other apps send invites.

Zapier triggers and actions
Step
Candidate SubmittedTriggerA candidate submits their answers.
Scores ReadyTriggerThe AI has finished with a candidate's answers: transcripts, a summary and, if the job is scored, the scores. Runs again if the results are redone, for example after you retry a recording that failed.
Label ChangedTriggerSomeone on your team labels a candidate Next round, Maybe or Not a fit, or clears the label.
Send Interview InviteActionInvites someone to one of your jobs. Pick the job from a list, map their email and, if you have it, their name. They get their own link by email.

Connect AnswerReel to Zapier

You need to be the Owner of an organization on Starter or above, because only the Owner can create API keys. Then:

  1. In AnswerReel, open Settings, then API and webhooks. Click Add AnswerReel to your Zapier account and accept the invite in Zapier.
  2. On the same page, create an API key and name it Zapier, so you know later what it's for. Copy it now: it's shown once.
  3. In Zapier, start a Zap and pick AnswerReel for the trigger or the action.
  4. When Zapier asks you to connect an account, paste the key. Zapier checks it by listing your jobs.
  5. Test the step, then turn the Zap on.

When you test a trigger, Zapier shows a sample candidate called Maya Ruiz rather than one of yours. AnswerReel has no list of recent candidates for Zapier to pull from, so your own data starts arriving once the Zap is on and a candidate submits, gets scored or gets a label.

What the triggers pass on

All three triggers hand the same fields to the next steps of your Zap, with the values as they are when the event is sent. There are no links to videos, audio or files.

Fields from AnswerReel triggers
name, emailThe candidate. Name can be empty.
job title, job idThe job they answered.
client name, client idThe client the job is for, if you've set one.
status, submitted atWhere the invite stands, and when they clicked Submit.
total scoreFrom 1.0 to 5.0. Empty until scoring is done, or when nothing could be scored.
scored questions, scorable questionsHow many questions got a score, out of how many could.
labelnext_round, maybe or not_fit, or empty.
review urlOpens the candidate in AnswerReel, for people in your organization.
candidate id, AI status, AI version, data version, event id, type, sequenceIDs and version numbers, for when you keep your own copy. The API docs explain each one.

Zaps you can build

Keep a spreadsheet of scored candidates
Scores Ready, then add a row to a Google Sheets or Excel spreadsheet with the name, email, job, total score and review link.
Tell the team when someone submits
Candidate Submitted, then post a message in Slack or Microsoft Teams with the job title and the review link.
Invite applicants from a form or your ATS
A new form entry or a new applicant in your ATS, then Send Interview Invite. If that person already has an open invite for the job, no second email goes out.
Move people on when you label them
Label Changed, then a Filter step that only continues when the label is next_round, then move the candidate to the next stage in your ATS.

Good to know

  • A score is a place to start reading, not a decision. Don't build a Zap that rejects or advances people on the score alone; have someone look at their answers first. The scoring method explains why.
  • When AnswerReel resends an event, the app skips it if it has already passed that event ID to your Zap. If that check fails, a repeat can run your Zap a second time.
  • Invites sent through Zapier count toward your plan's invite limits, the same as invites sent from AnswerReel. Each API key can make 60 requests a minute, so give Zapier a key of its own.
  • Each Zap with an AnswerReel trigger shows up in Settings, under API and webhooks, as a webhook added by Zapier. Turning the Zap off removes it.
  • If you move to a plan without Zapier, the triggers stop firing and the invite action returns an error that says why. Revoking the key stops the invite action, but triggers that are already on keep running: turn those Zaps off in Zapier, or turn their webhooks off in Settings.
  • Data you send to other apps is then kept by those apps. Deleting a candidate in AnswerReel doesn't delete those copies, and there's no Zapier trigger for deletions. If you need one, the candidate.deleted webhook covers it: A candidate's data was deleted. data carries only candidate_id and deleted: true.

Prefer to write your own code?

The Zapier app uses the public API: the same invite endpoint and the same events. The AnswerReel API docs cover authentication, every endpoint, the webhook format and how to check signatures.

Set up a job, then connect Zapier

Start from our screening interview questions, or build a scorecard first. Zapier, the API and webhooks come with Starter, $39 a month, and every plan above it.