INTEGRATIONS · EXPERTINI ATS

Zapier

A first-party Zapier integration for Expertini ATS — named hiring triggers, connected with your own API key.

2 min read · Updated July 2026 · Expertini Editorial

Every hiring team has a handful of "when X happens, do Y" wishes: post to a spreadsheet when a candidate is hired, ping a channel when a job goes live, add an applicant to a mailing tool. The Expertini ATS Zapier integration makes those recipes point-and-click: named triggers you pick from a menu, feeding real events from your hiring pipeline into the apps your team already uses.

It works the honest way: you generate an API key inside your own workspace, connect it in Zapier, and turn on Zaps. Six named triggers cover the hiring loop — job published, application received, pipeline stage changed, assessment submitted, video interview submitted, and video interview reviewed. The integration is in early access via a direct Zapier invite while it awaits listing in Zapier's public directory; ask us for the invite from the in-app hub. Prefer raw plumbing? The Webhooks app delivers the same events to any URL, and Data Export downloads your whole workspace as one JSON file.

▶ Watch the 30-second overview — no sign-up needed

01The gap this closes: hiring data trapped in one system

An ATS that cannot talk to the rest of your stack forces manual re-keying — the slowest, most error-prone step in any process. Event-driven automation removes it: the moment something happens in your pipeline, downstream systems know. With named Zapier triggers there is nothing to configure on the wire — pick the event, pick the destination app, done.

02How the connection works

Generate an API key on the Zapier page of the in-app hub — owners and admins control it, and can reveal, regenerate, or revoke it at any time. Zapier authenticates every request with that key; turning a Zap on subscribes it to your events automatically, and every subscription is listed (and removable) inside your ATS, alongside a full activity log of what fired and when. Included in the subscription from the Professional plan — see pricing for plans.

03Early access, honestly framed

The integration is fully built and running today, connected by direct invite link while it goes through Zapier's public-directory review. Being listed in the directory changes discoverability, not functionality — invited workspaces get the same six triggers the listed app will have. Progress is posted to What's New.

Engineering notes

Platform architecture & operations

A1Connection architecture

This app is configuration-based: what you save is acted on directly by the platform — no third-party account link is involved. Settings are validated on save, stored per organisation, and take effect on the next request.

Changes are immediate and reversible; removing the configuration stops the behaviour visibly. As with every connector, secrets (where any exist) are stored encrypted and shown only as presence flags.

A2Write semantics and data flow

Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.

Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.

Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.

A3Operational considerations

Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.

Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.

A4Placement in the integration topology

This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.

Dependency map

Connection typeconfiguration-based (no third-party account)

Secrets at restencrypted; UI shows presence flags, never values

Action journalats_app_activity — one row per action, vendor errors verbatim

Auto-push rulesoff by default, per-provider, every run logged

Registry statuslive

Interface blueprint

Structural schematic of the surface — panels, hierarchy, and interaction affordances. A contract, not a screenshot.

Connection card

● connected — presence flag

scopes: minimum required disconnect

Actions

push — explicit clickimport — deduplicated

Activity journal

Fig. 1 — Zapier: structural interface schematic. Panels and states are the contract; data shown is placeholder.

Interaction flow — states, validations, feedback

Every state below is enforced server-side; the interface reports it, it doesn't decide it.

Open app pageowner/admin only for changes

Save settingsvalidated on save (format, live checks where possible)

In effectnext request uses the new configuration

Journalactions logged to app activity

Invalid value → named validation error; nothing partial is savedRemoved configuration → behaviour stops visiblySecrets → presence flags only, never re-displayed

Fig. 2 — interaction flow: navy = states, gold = server-enforced gates, green = confirmed outcomes; tags list the edge cases and their feedback.

Organisation API used by the Zapier integration

X-API-Key: zap_<org>.<secret> — minted, revealed once, and revocable on the in-app Zapier page

GET /api/zapier/me/auth test — Zapier calls this when you connect

POST /api/zapier/hooks/subscribe a REST hook to an event

DELETE /api/zapier/hooks/<id>/unsubscribe (idempotent)

GET /api/zapier/samples/<event>/sample payload for the Zap editor

POST /api/zapier/candidates/create a candidate from a Zap action

$ curl -H "X-API-Key: zap_****.****" \
    https://ats.expertini.com/api/zapier/me/
{"org": "acme-recruiting", "ok": true}

$ curl -X POST https://ats.expertini.com/api/zapier/hooks/ \
    -H "X-API-Key: zap_****.****" \
    -d '{"event": "application.received", "url": "https://hooks.zapier.com/..."}'
{"id": "hk_1a2b", "event": "application.received"}

Responses abridged for illustration; endpoints and auth are the real contract. Dead subscriptions (HTTP 410) are pruned automatically.

Neighbouring connectors — Automation & Webhooks

Webhookslive Zapierthis page

Statuses come from the live registry — browse the full catalogue →

Frequently asked questions

Can I use Zapier with Expertini ATS today?⌄

Yes. The first-party integration is live in early access — request the Zapier invite link, generate your API key in the in-app hub, and turn on Zaps with named hiring triggers. The live Webhooks app remains available for custom endpoints.

What triggers are available?⌄

Six: a job goes live, a new application arrives, a candidate changes pipeline stage, an assessment is submitted, a video interview is submitted, and a video interview is reviewed.

Is my data locked into Expertini?⌄

No. The live Data Export app downloads your whole workspace as one JSON file at any time, at no extra cost.

Will the Zapier integration cost extra?⌄

No per-automation ATS fees — it is included from the Professional plan; your Zapier plan is governed by Zapier's own pricing.

At a glance

Live in early access — connect via direct Zapier invite
Six named hiring triggers, from job published to interview reviewed
Your own API key — reveal, regenerate, or revoke it any time
Every subscription and delivery logged inside your ATS
Webhooks app still available for custom endpoints
No per-automation or export fees on the ATS side

See zapier on your own hiring.

Bring a real job description to a 30-minute demo — free trial included.

Book a demo