INTEGRATIONS · EXPERTINI ATS

Calendar Invites (.ics)

Download a standard .ics invite for any scheduled interview — works with Google, Outlook, and Apple Calendar, no account connection needed.

2 min read · Updated July 2026 · Expertini Editorial

Interviews fail for mundane reasons more often than dramatic ones — and the most mundane of all is the meeting that never made it into someone's calendar. The Calendar Invites app closes that hole with the most dependable tool in scheduling: the .ics file. Every interview scheduled in Expertini ATS can be downloaded as a standard calendar invite that opens in Google Calendar, Outlook, and Apple Calendar alike.

The gap this closes is the no-show caused by manual calendar entry — a recruiter schedules the interview in the ATS, then someone retypes the time into a calendar, and a typo or a timezone slip later, the panel is waiting for a candidate who thinks the interview is tomorrow. The .ics file carries the exact date, time, and details from the interview record, so what lands in the calendar is what the ATS says. Crucially, it needs no account connection at all: no OAuth grant, no IT approval, no calendar permissions. It works for every organisation from the first day, as part of the same interview scheduler your pipeline already uses.

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

01The format every calendar understands

The .ics (iCalendar) format has been the universal interchange standard for calendar events for decades. Google Calendar, Outlook, Microsoft 365, Apple Calendar, and virtually every other client import it natively — usually with a single click or tap on the file.

That universality is the point: your interviewers and candidates use different providers, different companies' IT policies, and different devices. One file format serves all of them without asking anyone to connect an account.

02Zero-permission scheduling

Connected-calendar integrations are powerful, but they require each user to grant access — which stalls in organisations with strict IT policies or external interviewers such as client hiring managers. The .ics download has no such dependency. Schedule the interview, download the invite, attach or forward it — done. Agencies coordinating interviews with client-side panels find this especially painless.

03Fewer no-shows, cleaner pipeline

An interview in everyone's calendar is an interview that happens, with reminders handled by each person's own calendar client. That keeps your hiring pipeline moving on schedule and your interview stages meaningful. Everything here is included in the subscription — no scheduling add-on, no per-invite cost. Get started with a free signup.

Engineering notes

Platform architecture & operations

A1Connection architecture

The connection model for this integration is stated honestly on its card: where a public API exists it is used with your own account and consent, and where a vendor requires a partner agreement the page says so instead of showing a Connect button that cannot work.

Once available, credentials follow the platform standard: encrypted at rest, presence-flag display, immediate removal on disconnect.

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 typestated per-vendor on the card

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 — Calendar Invites (.ics): 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.

Connectowner/admin clicks Connect on the Connectors page

Vendor consentthe vendor's own screen lists the exact scopes

Token exchangeserver-side callback; secrets never touch the browser

Connectedencrypted store; card flips with presence flag

Explicit actionspush / import / schedule — each one journalled

Consent denied → the vendor's error code surfaces in a toast, namedPlatform keys missing → honest setup pointer, not a silent bounceToken expired → automatic refresh at the chokepointRefresh rejected → visible reconnect prompt, features never break silentlyPlan below minimum → lock card names the exact plan

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

Frequently asked questions

Which calendar apps can open the .ics file?⌄

Effectively all of them — Google Calendar, Outlook and Microsoft 365, Apple Calendar, and any other client that supports the iCalendar standard, which has been universal for decades.

Do interviewers or candidates need to connect their calendars?⌄

No. That is the point of the .ics approach — no OAuth connection, no permissions, no IT approval. Anyone who can open a file can add the interview to their calendar.

What details does the invite contain?⌄

The interview's date, time, and details exactly as scheduled in the ATS, so the calendar entry always matches the interview record — no retyping and no timezone slips.

Is this a paid add-on?⌄

No. Calendar invites are part of the interview scheduling built into every Expertini ATS subscription, with no per-invite or per-seat scheduling fee.

At a glance

Standard .ics invite for every scheduled interview
Opens in Google, Outlook, and Apple Calendar
No account connection or IT approval needed
Exact times from the interview record
Ideal for external and client-side interviewers
Included with built-in interview scheduling

See calendar invites (.ics) on your own hiring.

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

Book a demo