Integrations

01Genuinely native, not an integration

Publishing a job to the country-site network, the automated video and thumbnail generation pipeline, sitemap distribution, and dual-registration sync that creates a matching candidate account on the destination country's own job site are not third-party integrations in any normal sense. They're the same infrastructure the ATS itself runs on, which is why they require no separate setup, API key, or configuration step; publishing a job simply is writing into that infrastructure directly.

02Real third-party integrations already live

Google is one of two largest connections: one OAuth sign-in covers Google Calendar and Google Meet (an interview gets a real Meet link automatically when you pick it as the provider), Google Drive (candidate CVs sync to your own Drive on demand), and YouTube (job videos publish as Shorts). Microsoft is the other: Entra ID sign-in, Outlook Calendar and Teams meeting links for interviews, and OneDrive CV sync work the same way under your own Microsoft 365 tenant. Slack and WhatsApp Business notify your team and message candidates on channels they already check. Facebook and Instagram publish the auto-generated job video straight to your Page. Google Ads, Microsoft Ads, and Google Analytics 4 connect your paid distribution and traffic reporting. Custom SMTP lets you send candidate email from your own domain, and Webhooks expose every pipeline event to whatever automation tool you run — Zapier and n8n included, without waiting on a purpose-built connector.

Stripe handles subscription billing and the self-service billing portal, and Gemini, Google's AI model family, powers the semantic extraction step described on the CMS and AI Recruiting pages — both real external dependencies, not built in-house, governed by their own providers' service terms.

03API-first underneath

Every screen in the product — jobs, candidates, applications, scores, interviews, offers, reports — is driven by JSON API endpoints the frontend itself calls, rather than server-rendered pages with logic baked into the template. This matters for anyone considering deeper integration work: the API surface the UI depends on already exists and is stable, rather than needing to be built out separately for programmatic access.

04What's still on the roadmap

Zoom, Dropbox, LinkedIn and X posting, DocuSign for offer e-signature, and native HRIS/payroll/accounting connectors (Xero, QuickBooks, background-check providers) are built end-to-end in the product but not yet registered with their respective platforms — they will go live without a product change once that registration completes. None of these are secretly present under a different name; the Apps & Integrations directory marks each one plainly as live or roadmap, and that status only ever moves in one direction.

05How to think about 'native' versus 'integration' when evaluating any ATS

The distinction matters beyond Expertini specifically. A native capability generally means lower operational risk (no external API to fail, rate-limit, or deprecate on someone else's schedule) but less flexibility to swap providers later. A genuine third-party integration usually means more choice and portability but adds a dependency whose reliability, pricing, and roadmap you don't control. Neither is categorically better — a payroll integration should almost certainly be a genuine third-party connection to whatever payroll system an organisation already trusts, while job distribution benefits from being native precisely because there's no reason to introduce an external dependency for something the platform can do directly.

When evaluating any vendor's integration claims, the useful question isn't "how many integrations do they have" but "which of these are genuinely external systems, and which are just internal features marketed with integration language to sound more extensive than they are." We've tried to answer that question plainly for our own product on this page rather than making you guess.