The integrations your AI interview software should have shipped on day one.
Greenhouse, Lever, Workable, Airtable, and Google Sheets — all native, all live. Candidates pull in when they apply. Transcripts, rubric scores, and status updates push back the moment the interview ends. No Zapier tax. No polling lag. No manual export.
Inbound · scored report lands in Vettika seconds after hangup
Native connectors
5 native connectors, 1 generic webhook.
Every connector is built and maintained by Vettika — not a third-party integration layer. Structured field mapping, real-time pushes, and audit logs that actually tell you what happened.
Greenhouse
Pull active applications straight from Greenhouse Harvest with your API key. Filter by job, preview the candidates before importing, and screen them without a CSV round-trip. Scored results live in Vettika — write-back to Greenhouse is not shipped yet.
Lever
Connect with your Lever API key and pull Opportunities in. Preview before importing so you choose who gets screened. Transcripts and rubric scores stay in Vettika — posting a Lever feedback form is not shipped yet.
Workable
Authenticate with your Workable API key and pull candidates in, filtered by job. Preview before importing. Evaluation data stays in Vettika today — nothing is written back to the Workable record.
Airtable
Map any Airtable base and table as your candidate source, map the columns, and preview before importing. Built for ops teams already using Airtable as a lightweight ATS. Results are read in Vettika, not written back to the base.
Google Sheets
Authenticate with Google OAuth, pick a sheet, map your columns and import candidates on demand. No API key setup, no service accounts. Vettika reads the sheet; it does not write back to it.
Generic Webhook
Any system that can POST JSON can push candidates into Vettika, on a per-recruiter URL with HMAC signature verification and configurable field mapping. Inbound only — Vettika does not yet deliver results back out over a webhook.
Sync flow
From application to scored record in four steps.
Connect once. Every candidate from that point flows through automatically — no recruiter touch between application and scored report.
Connect your ATS
OAuth or API key in Settings → Integrations. Credentials are AES-256-GCM encrypted at rest. Connection health visible at a glance.
Candidates pull in
Pick a job, preview the candidates the connector found, and import the ones you want. Interview invites dispatch from there — no CSV, no copy-paste.
The report lands in seconds
The moment the call ends, the timestamped transcript, per-criterion rubric scores and overall recommendation appear in your Vettika dashboard. They stay in Vettika — nothing is written to the source record.
Automation advances
Score thresholds are configurable per campaign. Above-threshold candidates advance in Vettika; below-threshold can auto-decline with optional improvement tips. Stage changes happen in Vettika, not in your ATS.
Data fields
What moves in. What comes out.
Candidates come in from your ATS with no CSV export and no lost context. The scored report comes out in Vettika, where you read it, export it, or act on it with an automation rule. Write-back into your ATS is not shipped yet.
Inbound — ATS → Vettika
- Candidate name + contact email
- Job title / req number
- Source and current pipeline stage
- Application date
- Custom ATS fields (mapped per integration)
- Resume link or parsed resume text
Produced in Vettika
- Full transcript, timestamped per turn
- Rubric score per criterion (0–10)
- Overall recommendation (Advance / Hold / Decline)
- Interview duration + completion status
- Exportable audit log entry with timestamp + actor
All data handling is documented in the AEDT bias audit disclosure. Agencies can connect a separate ATS per client account.
Why native beats middleware
Skip the Zapier tax.
Zapier-based ATS glue was the only option in 2019. In 2026 it is a compliance liability, a latency problem, and a line item that compounds as you scale.
No middleman on the way in
Candidates come straight from your ATS into Vettika on demand. A Zapier hop adds a polling interval, a second vendor and a second place your candidate data lives.
No intermediate data storage
Candidate PII travels directly between Vettika and your ATS. Zapier stores a copy of every payload in their logs — a liability under GDPR, CCPA, and data-residency requirements.
Structured field mapping
Every field maps to a named ATS field with type validation. Zapier passes freeform JSON blobs that silently mismap when the ATS schema changes.
No silent failures, no per-connector cost
Native connectors surface errors in your integration dashboard with full retry history. Zapier charges per task and drops tasks silently when limits are hit.
See how recruiters and agencies use native integrations to eliminate manual handoffs.
Competitor comparison
How Vettika integrations compare.
Enterprise video-interview platforms lock integrations behind six-figure contracts. Vettika ships native inbound connectors on every paid plan. See pricing.
| Feature | Vettika | HireVue | Hireflix | Karat |
|---|---|---|---|---|
| Greenhouse native | Yes — inbound | Enterprise contract | Yes — one-way | Coordinator-managed |
| Lever native | Yes — inbound | Enterprise contract | Yes — one-way | No |
| Workable native | Yes — inbound | No | No | No |
| Airtable native | Yes | No | No | No |
| Google Sheets | Yes | No | No | No |
| Generic webhook | Yes — inbound | No | No | No |
| Setup time | Under 5 min | Weeks (IT) | ~30 min | Weeks |
| Price to unlock | Any paid plan | Enterprise quote | $149+/mo | $8k–$20k/req |
FAQ
Integration questions, answered.
Does it work with Greenhouse multi-org accounts?
Yes. You connect at the company level using a Greenhouse Harvest API key scoped to the relevant org. If you manage multiple Greenhouse companies, connect each separately — each maps to a distinct Vettika workspace. There's no limit on connections per plan.
Will connecting Vettika mess up my ATS pipeline stages?
No — Vettika does not write to your ATS at all today. The connectors read candidates in; nothing moves a candidate, changes a stage, or edits a field on your side. Automation rules act on the pipeline inside Vettika only. If ATS write-back matters to you, say so and we will record the demand rather than imply it already works.
What happens to my data if I disconnect an integration?
Disconnecting revokes the stored token immediately and stops all future imports. Existing transcripts and scored reports in Vettika are retained according to your plan's retention policy. Nothing in your ATS changes, because Vettika never wrote to it.
Do you support Workday, iCIMS, or SAP SuccessFactors?
Those enterprise systems are on the roadmap for Q4 2026. In the meantime, every major ATS exposes an outbound webhook — point it at Vettika's inbound webhook connector to push candidates in today. Setup takes under 10 minutes and supports configurable field mapping.
How is the ATS connection secured?
All stored credentials (API keys, OAuth tokens, refresh tokens) are encrypted with AES-256-GCM before being written to the database. Tokens are never logged, never exposed in error messages, and never returned to the client after initial save. If a token expires or is revoked, the next import surfaces the error on the connection.
Connect your ATS. Run your first interview free.
Native integrations are available on every paid plan. Your first interview is free — no credit card, no demo call, no IT ticket. Connect Greenhouse, Lever, Workable, Airtable, or Google Sheets in under 5 minutes.