INTEGRATIONS · EXPERTINI ATS

PDF Job Brochure

Generate a branded PDF of any published job — for job fairs, recruiters, and offline sharing.

2 min read · Updated July 2026 · Expertini Editorial

Not every candidate conversation happens on a screen. Job fairs, campus visits, agency briefings, and referral chats all need something you can hand over — and a URL scribbled on a notepad is not it. The PDF Job Brochure app generates a branded, print-ready PDF of any published job in one click: your logo and colours, the full role description, and the apply link on the page.

The gap this closes is the offline dead end in an otherwise digital pipeline. A strong conversation at a careers fair evaporates if the candidate has nothing to take away; a recruiter briefing a client from memory undersells the role. The brochure turns any job into a portable artefact that always matches the live listing, because it is generated fresh from the job record at the moment you download it — never a stale copy from someone's desktop. It is included in every subscription, with no per-document fees and no design tool required. Write the role once — the job description builder helps get it right — and the brochure inherits it.

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

01Branded without a designer

The brochure applies your organisation's branding — logo and identity from your ATS settings — to a clean, professional layout automatically. Hiring managers get consistent, on-brand collateral without waiting on a design team or wrestling with a template in a word processor.

Because generation is instant and per-request, editing the job and re-downloading takes seconds. Last-minute salary change before the fair? The next download reflects it.

02Where paper still wins

Careers fairs and campus events are the obvious cases, but brochures also travel well by email: agencies share them with candidates who are not actively browsing job boards, and employees forward them with referrals. Each brochure carries the job's apply link, so the offline handoff ends back in your online hiring pipeline where applications are tracked and scored.

03Always fresh by design

Brochures are generated on demand from the live job record rather than stored as files. There is no version drift, no folder of outdated PDFs, and no risk of circulating a brochure for a role that changed last week. Agencies managing roles for multiple clients can pull a current brochure per client engagement alongside the client CRM.

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 — PDF Job Brochure: 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

What does the brochure include?⌄

The published job's title, full description, key details, and apply link, laid out with your organisation's branding. It is generated from the live job record, so it always matches what candidates see online.

Do I need design software or a template?⌄

No. The layout is built in. You click download on a published job and receive a print-ready PDF — no design skills, licences, or external tools involved.

Can I regenerate a brochure after editing the job?⌄

Yes, instantly. Brochures are created fresh on every download, so the latest edit is always what prints. There is no cached old version to chase down.

Is there a limit or per-document charge?⌄

No. Brochure generation is included in your subscription — generate as many as you need for as many jobs as you run.

At a glance

One-click branded PDF for any published job
Print-ready for fairs, campuses, and briefings
Apply link keeps offline handoffs trackable
Regenerates fresh on every download
No design tools or templates needed
Unlimited generation, included in every plan

See pdf job brochure on your own hiring.

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

Book a demo