Zapier and Make link Test Candidates to thousands of other apps, such as your ATS, Google Sheets, Slack or your CRM, without writing code. You build a small automation: when something happens in one app, do something in another.
What you can do
Triggers (something happened in Test Candidates):
- Assessment completed: a candidate finished every test on an assessment.
- Test completed: a candidate finished one test.
- Result unlocked: a result was unlocked, so its scores are now available.
- New candidate: someone new became a candidate in your workspace.
Actions and searches (do something in Test Candidates):
- Invite a candidate to an assessment. They get the usual invitation email. Someone already invited is not invited again.
- Find a candidate by email, with their assessments and results.
Make also has Make an API call, for anything else the API can do.
Scores stay empty until a result is unlocked, the same as everywhere else in Test Candidates. If you want scores, use Result unlocked rather than Test completed.
Set it up
- In Test Candidates, go to Settings, then Integrations, and create an API key. Copy the key and the secret, as the secret is shown once.
- On the same page, click Add to Zapier or Add to Make, and accept the invitation.
- In Zapier or Make, add a Test Candidates step. When it asks for a connection, paste the key and the secret.
Only admins can create API keys. Anyone with the key can see your candidates and invite people, so keep it private. See Keep your API key safe.
Example: send finished results to a spreadsheet
- Trigger: Test Candidates, Result unlocked.
- Action: Google Sheets, Add row, mapping the candidate's name, email, test name and score.
Example: invite candidates from your ATS
- Trigger: your ATS's "candidate moved to stage" event.
- Action: Test Candidates, Invite a candidate to an assessment, choosing the assessment and mapping the candidate's email and name.