INTEGRATIONS · EXPERTINI ATS

Microsoft Word Offer Export

Export any offer letter as an editable .docx in your OneDrive — or save the finished PDF to OneDrive or Google Drive — from the same offers screen.

2 min read · Updated July 2026 · Expertini Editorial

Offer letters have two lives. Before signature they get negotiated — legal wants a clause changed, the manager wants the start date moved — and that editing belongs in Word, where your templates, tracked changes, and approvals already live. After signature they get archived, and that belongs in your document storage, not a download folder. The Word export serves both lives from the offers screen: one click exports the letter as an editable .docx into your OneDrive, and its sibling buttons save the final PDF to OneDrive or Google Drive.

Like the Excel export, this uses the Microsoft connection your organisation already has — Microsoft's official Graph API, your own account, your own storage. Word and OneDrive are trademarks of Microsoft Corporation; Google Drive is a trademark of Google LLC; the documents created are yours in every sense that matters.

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

01How to use it

On the offers page, each offer row carries three cloud actions: Export to Word (OneDrive) produces the editable .docx; Save PDF to OneDrive and Save PDF to Drive archive the rendered letter where your documents live. Files land in the "Expertini ATS" folder of the connected account and the response links you straight there. Not connected yet? The button walks you to Connectors first — the guided flow never dead-ends.

02Editable before, immutable after

The .docx export contains the full letter text — candidate, role, salary, terms — as a clean document your team edits like any other Word file. The PDF exports capture the letter as rendered, which is what belongs in the personnel file after acceptance. Using both gives you the negotiation copy and the archival copy without either pretending to be the other.

03Where e-signature fits

Signature itself runs through the e-signature integration with pre-filled recipient and document fields. The Word export complements it for teams whose legal process wants a red-lined draft stage before anything is sent to sign — draft in Word, finalise in the ATS, send for signature, archive the PDF. Every step logged.

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 — Microsoft Word Offer Export: 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.

Neighbouring connectors — Documents

Google Sheetslive Google Docslive Microsoft Excellive Microsoft Wordthis page

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

Frequently asked questions

Is the exported file a real Word document?⌄

Yes — a standards-compliant .docx with the letter as editable paragraphs, generated server-side. No macros, no add-ins, opens in Word desktop, web, and compatible editors.

Where exactly do files land?⌄

In the "Expertini ATS" folder of the connected account's OneDrive (or Google Drive for the Drive PDF button), created automatically on first use.

Can I save the PDF to both OneDrive and Google Drive?⌄

Yes — the buttons are independent, so belt-and-braces archiving across both clouds is one extra click.

Does editing the .docx change the offer in the ATS?⌄

No — the export is a copy for your document workflow. The ATS offer record remains the system of record; update it there and re-export if terms change.

Extra cost?⌄

None — included in the plan, no per-document fees.

At a glance

One-click editable .docx of any offer letter into OneDrive
Save the rendered PDF to OneDrive and/or Google Drive
Files organised under an auto-created "Expertini ATS" folder
Complements e-signature: draft in Word, sign digitally, archive the PDF
Push-to-connect guidance if Microsoft isn't linked yet
Official Graph API, your account, your storage — no middleware

See microsoft word offer export on your own hiring.

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

Book a demo