Appearance
Zapier and Make
Who can do thisWorkspace owners and admins
Calling Infyva from Zapier or Make needs an API key, which is on Enterprise.
Infyva sends a signed webhook when something happens. Zapier and Make catch it and pass it on to the apps you use. Our public API covers the other direction.
There is no Infyva app in the Zapier or Make directories. You connect with the webhook tools both products include.
To see these steps in Infyva: in the sidebar, click Settings, then Integrations, then Setup steps on the Zapier or Make card.
Start a Zap from Infyva events
- In Zapier, create a Zap. For the trigger, choose Webhooks by Zapier and the event Catch Raw Hook. Raw keeps the body intact so you can check the signature.
- Copy the webhook URL Zapier gives you.
- In Infyva, open Settings > API keys and webhooks. In Webhooks, paste the URL, tick the events you want and click Add endpoint. Copy the signing secret if you plan to check signatures.
- Click Send test next to the endpoint, then click Test trigger in Zapier so it learns the fields.
- Add the actions you want, for example post to a Slack channel, add a row in Google Sheets or update a record in your HRIS.
Start a Make scenario from Infyva events
- In Make, create a scenario and add the Webhooks module, Custom webhook. Click Add to create one.
- Copy the webhook address Make shows.
- In Infyva, open Settings > API keys and webhooks. In Webhooks, paste the address, tick the events you want and click Add endpoint.
- In Make, click Re-determine data structure, then click Send test in Infyva so Make learns the fields.
- Add the modules you want after the webhook and turn the scenario on.
Events you can trigger on
| Event | When |
|---|---|
interview.completed | A candidate finishes an interview. The report follows a minute or two later. |
report.ready | The interview report and score are ready. |
candidate.stage_changed | Someone moves a candidate to another stage on a job. |
flag.raised | A report has a high-risk integrity result for a person to review. |
The fields in each event, the headers and the signature are on Webhooks. Failed deliveries retry after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours.
Test events have a different shape
Send test sends a webhook.test event whose data holds only a message. Zapier and Make learn the fields from that test. To map fields such as overall_score, run one real interview first or add them by hand.
Call Infyva from Zapier or Make
To create candidates or schedule interviews from a Zap or scenario, use an Infyva API key. API keys are on Enterprise.
- In Zapier, use the Webhooks by Zapier action Custom Request.
- In Make, use the HTTP module Make a request.
Send the header Authorization: Bearer <your API key>. Create keys in Settings > API keys and webhooks. See Public API for the base URL.
| What | Request |
|---|---|
| List jobs | GET /jobs |
| Add a candidate to a job | POST /jobs/{job_id}/candidates |
| Schedule an interview | POST /jobs/{job_id}/candidates/{candidate_id}/interviews |
| Get an interview | GET /interviews/{interview_id} |
| Get the report | GET /interviews/{interview_id}/report |
These paths go after the base URL, which ends in /api/v1/public. The full base URL is shown in Infyva on the integration's setup page and under API reference on the Developer platform page.