Make integration

Turn any document in your scenario into a tracked link

The EveryPage app for Make (ex-Integromat) works in both directions: instant triggers push reads, downloads, and form fills into your scenario within seconds, and 19 modules turn PDFs from 2,000+ apps into tracked links - with GDPR-friendly analytics: no cookies, no reader IP addresses stored.

See the developer API Compare plans

How the integration works.

The app connects with a personal API key - no OAuth dance, no admin approval - and then works in both directions: EveryPage pushes reader activity into your scenarios, and your scenarios create and manage tracked documents in EveryPage.

1
Connect with an API key
Add EveryPage to a scenario and paste an API key from your account page (Account -> API keys -> create one named "Make"). The key works on every plan, is only ever sent to everypage.co, and the connection is labelled with your account email and plan so multiple accounts stay distinguishable.
2
Pick a module
Nineteen modules cover both directions: instant watch modules that start scenarios from reader activity, actions that upload PDFs and manage live links, searches to find documents by name, and a universal "Make an API Call" module for anything else the EveryPage API can do.
3
Turn the scenario on - the plumbing manages itself
Activating a scenario with an instant watch module registers a dedicated webhook on your account automatically; deactivating removes it, and an already-deleted webhook never errors your teardown. Every live subscription stays visible under Account settings.

Under the hood

Instant where it matters, frugal where it counts

Reads, downloads, and form fills arrive over dedicated webhooks within seconds of the event - no operations spent polling for them. A Watch Events polling fallback exists for scenarios that prefer scheduled pulls, and because Make prices by operations, its recommended schedule is 15 minutes.

GDPR-friendly by architecture

EveryPage readership is measured without cookies and reader IP addresses are never stored - each reader gets a salted, pseudonymous identity instead, with country resolved in flight. Document analytics from a UK-operated tool that your GDPR review can cover in a paragraph, not a project.

Three share channels from every upload

Every document a scenario creates comes back with a share link, a QR code image URL, and an embed code - all keyed to the document itself, never a renameable slug. Replace the file behind the link and the printed QR poster, the embedded viewer, and the emailed URL all keep working.

Signed at the source, honest about Make

Every webhook delivery is HMAC-signed by EveryPage. Make modules cannot verify raw-body signatures, so inside Make authenticity rests on the unguessable per-scenario webhook URL Make generates - we say that plainly rather than imply otherwise. The signing secret is stored with the webhook, ready for the day Make exposes raw bodies.

Instant triggers: when this happens in EveryPage.

Dedicated webhooks push each event into your scenario within seconds of it happening - no polling operations, no missed reads.

Watch Reads

Instant

A reader finished viewing a document - with pages viewed, time spent, country, and link-variant attribution, ready to map into the next module.

Watch Downloads

Instant

A reader (not you) saved a copy. Log it, score it, or follow up on it.

Watch Form Fills

Instant · Pro

A viewer completed the email gate or lead form. Every captured field rides along, with the email copied to a top-level key for easy mapping into your CRM.

Watch Events

Polling

The scheduled fallback: cursor-walks the events feed for reads, downloads, and form fills. Make prices by operations, so a 15-minute schedule is the sweet spot.

Modules: make EveryPage do this.

Create, manage, measure, and export tracked documents from any of the 2,000+ apps on Make.

Upload a File

Map a file from any module and get the share URL, QR code, and embed code back - with the full plan-aware settings surface: viewer mode, passcode, expiry, protection toggles, email gate, vanity slug, watermark, page range.

Update File Settings

Change any subset of settings on an existing document - only the fields you provide are sent, and the link never changes.

Get a File / List Files

Look a document up by name or list them all, and feed the result into the rest of the scenario.

Replace File Content

Pro

Swap the PDF behind a live link - the link, QR codes, embeds, settings, and readership history all survive.

Link Variants

Pro

Create, list, update, revoke, and delete per-recipient tracked links - one document, per-person readership, GDPR label redaction included.

Get a QR Code

The tracked QR code as a PNG file, ready to map into print, merge, or email modules.

Get a Readership Summary

The plan-shaped analytics rollup for a document - views, readers, completion - as mappable fields.

List Events

Bulk pulls from the events feed with cursor paging - built for data-store and warehouse scenarios.

Delete a File

Trash by default - restorable until the purge date - or permanently purge when your workflow decides it is done.

Make an API Call

The universal module: any EveryPage API endpoint, with your connection already authenticated.

Five scenarios to build first.

The scenario templates that ship with the app - each one a pattern you can rebuild in minutes.

Watch Form Fills → CRM

Gated deck → CRM upsert

A prospect completes the email gate on your deck and lands in your CRM with every captured field - while they are still reading.

Drive / Dropbox → Upload a File → Email

Client PDF → tracked link → email

A deliverable lands in a Drive or Dropbox folder, becomes a tracked EveryPage link, and goes out by email - so you can prove the client read what you billed for.

Watch Reads → Slack

Document read → Slack ping

The moment someone finishes reading, the channel hears about it - which document, how many pages, and for how long.

Schedule → Readership Summary → Sheets

Weekly readership → Google Sheets

Every Monday, pull the readership rollup for the documents you care about into a running spreadsheet - trends without dashboard visits.

Upload a File → List Events → Data store

Invoice → tracked link → data store

Generated invoices and reports go out as tracked links, and the events feed writes engagement back to a Make data store - a paper trail that includes reading.

What each plan unlocks.

The Make app is free to connect on every EveryPage plan. Fields that need a higher plan say so in their description, and if a scenario trips a plan gate anyway, the error names the plan and links the upgrade page - never a bare status code.

In the Make app	Free	Basic	Pro
Watch Reads, Watch Downloads & Watch Events triggers	✓	✓	✓
Upload, Update Settings, Get/List, QR, Readership, Events & Delete modules	✓	✓	✓
Protection toggles on upload (block right-click, print, copy)	—	✓	✓
Watch Form Fills (email gate & lead form captures)	—	—	✓
Link Variants & Replace File Content modules	—	—	✓

Make questions.

What can I automate with the EveryPage Make integration?

Both directions of a document workflow. Instant triggers start scenarios the moment a document is read, downloaded, or unlocks an email gate; modules let 2,000+ Make apps upload PDFs and get tracked links back, update settings on live links, mint per-recipient link variants, replace content behind a link, pull QR codes and readership summaries, export bulk events, and delete files - plus a universal API-call module for everything else.

Is EveryPage a DocSend alternative with a Make integration?

Yes - and an uncontested one: DocSend has no Make app at all. If tracked document links belong in your scenarios, EveryPage covers the job with instant read, download, and form-fill triggers plus a full set of upload and management modules - at a flat price instead of per-user billing, with analytics that store no reader IP addresses.

Are the triggers instant or polled?

Reads, downloads, and form fills are instant - EveryPage pushes them over dedicated webhooks within seconds, costing you no polling operations. A Watch Events polling module exists as a fallback (a 15-minute schedule is recommended, since Make prices by operations). Deliveries are HMAC-signed at the source; because Make cannot verify raw-body signatures, authenticity inside Make rests on the unguessable per-scenario webhook URL.

Is the document analytics GDPR-friendly?

That is the design. Readership is measured first-party inside the EveryPage viewer with no cookies and no third-party scripts, and reader IP addresses are never stored - each reader gets a salted, pseudonymous identity, with country resolved in flight and the address then discarded. EveryPage is UK-operated, and there is nothing here for a consent banner to disclose.

Is the app live in the Make app directory - and which plans do I need?

The app is built and going through Make's review for a public listing, so it is not in the app directory yet - and until it is, everything on this page is also reachable from Make's HTTP modules against the EveryPage API (see the developer docs). On the EveryPage side every plan connects, free included; Watch Form Fills, Link Variants, and Replace File Content are Pro because the product features they drive are Pro.

Do tracked links have to expire?

No - expiry is a control you set per document, never a default. Give a link an expiry date, a view budget, or neither; on Pro, links can be set to never expire. Scenarios can also manage expiry for you: have your CRM expire the proposal link when the deal closes, straight from Update File Settings.

Put a tracked link in every scenario.

Connect EveryPage with an API key, drop a module into the flow, and the next document your scenario sends will report back - reads, downloads, and leads, within seconds.

Compare plans