Infyva and Workable: AI interviews for every candidate

At a glance

How you connect it

Workable connects with an access token, not a sign-in window. One connection serves the whole workspace. Only an owner or admin can create it, and everyone on the team can import jobs afterward.

1. In Workable, open Settings, then Integrations, then Apps, and generate an access token.
2. Give it the r_jobs, r_candidates and w_candidates scopes.
3. In Infyva, open Settings, then Integrations, choose Workable, and enter the part of your Workable address that comes before .workable.com, plus the token. Use Test connection to check them.

Add a Workable member ID if you want Infyva to write back. Workable records stage moves and comments as a member, so Infyva needs to know which one. Leave it blank and Infyva imports only: candidates come in, nothing is written to Workable. The connection settings show clearly whether write-back is on or off. The token is encrypted and never shown again.

What comes in from Workable

Infyva lists your published jobs. Pick one and import it as a new Infyva job, or map it onto a job you already have. Import again any time to pull in new candidates. Nobody is imported twice, because Infyva matches on the Workable candidate and then on the email address inside the job.

• The job description. Infyva reads it from the job and uses it to write the interview questions. Without a usable description, the job imports but resumes are not scored until you add one.
• The candidate. Name, email, phone and the current Workable stage. Disqualified candidates are skipped. In Workable a candidate belongs to one job, so the candidate and the application are the same record.
• The resume. Infyva looks it up and downloads it in the background, reads it, and scores it against the job.

Workable allows a limited number of requests every few seconds for each token. Infyva spaces its calls to stay inside that limit. On a big job the candidate list arrives first and the resumes follow, a few at a time. If Workable asks Infyva to wait, the rest simply carries on in the next run, with no need to start the import again.

Sending the interview

Invite from Infyva as usual, or let Workable trigger it. In the job's stage mapping, choose the Workable stage that should send the interview. When a candidate reaches it, the next sync or webhook sends the invite. Candidates already at that stage are invited on the next sync, and each candidate is invited once.

An automatic invite follows the same rules as any other. It uses a credit, it respects your company's AI hiring policy for the job's location, and it is skipped, with the reason in the sync log, when the record has no email address or the workspace is out of credits.

What goes back to Workable

• Status comments. A comment on the candidate when the interview is scheduled and another when it is completed.
• The result. When the report is ready, a comment with the score out of 100, a short summary and a link to the full report. A report held for a person to review has no overall score, so nothing is sent rather than a made-up number.
• Stage moves. When you move a candidate in Infyva, Infyva moves them to the matching Workable stage.

Results arrive as a comment on the candidate. The per-skill scores, recordings and integrity evidence stay in the Infyva report that the comment links to.

Stage mapping

Each job maps Infyva's stages (Applied, Screened, Interviewed, Offer, Hired and Rejected) to the stages on that Workable job. Leave a stage on "Match by name" and Infyva picks the closest Workable stage name, or choose "Don't move in the ATS" to leave a stage alone. When nothing matches, Infyva moves nothing and writes the reason to the sync log.

How often it syncs

Webhooks are optional. If you add them, Workable tells Infyva about new candidates and moves within about a minute. Workable takes one event for each subscription, so you add two: one for a new candidate and one for a candidate who moves. Workable signs its deliveries with the access token, so you paste that same token into the webhook field in Infyva. Infyva refuses any delivery whose signature does not check out. Without webhooks, mapped jobs re-sync about every six hours, and you can press Sync now at any time.

Updates that Workable cannot take right away are retried on their own for up to about nine hours. The sync log lists every import, webhook and update, and a failed one can be retried by hand.

What it does not do

• It does not write per-skill scores or recordings into Workable. They stay in the Infyva report behind the link.
• It writes nothing back until you add a Workable member for write-back.
• It does not hire, reject or decide anything. People make those calls.

Plans, credits and disconnecting

The Workable connection is on Pro and Enterprise and is switched on during the 14-day Pro trial. It costs nothing extra, and interviews are paid in credits like any other. See pricing.

Disconnecting deletes the stored token, the queued updates and the Workable links on your jobs and candidates. You can also remove imported candidates who never had an interview. Anyone who did have one stays, unlinked, because their results are your records.

Using something else? See all integrations, the Lever and Ashby guides, or watch the 30-second demo.