Zapier
Connect EveryPage to Zapier to automate document uploads, manage sharing settings, and respond to reader activity.
The EveryPage Zapier app uploads documents, updates sharing settings, starts Zaps from reader activity, and pulls readership summaries.
Access
The app is usable but not listed in the Zapier App Directory — searching Zapier for "EveryPage" will not find it. Access is by invite link: sign in to EveryPage, open your Account page, and use the Zapier early-access link in the banner above your API keys. Opening that link adds the app to your Zapier account.
Authentication
To connect your EveryPage account to Zapier, you need an API key. API keys are master credentials—treat them like a password.
- Sign in to your EveryPage account and go to Account.
- Under API keys, create a new key (or copy an existing one).
- In Zapier, when setting up an EveryPage action or trigger, paste this key into the API Key field.
- Zapier tests the key against your current-user endpoint to confirm it works.
For more details on API keys, see the API keys guide.
Triggers
Triggers fire when a specified event happens to one of your documents. Each trigger can optionally filter to a single document or watch all your documents.
| Trigger | Type | Description | Availability |
|---|---|---|---|
| New Document Read | Polling | Walks the view events feed; one event per completed read session | Free |
| New Document Read (Instant) | Webhook | Same event delivered instantly — a file.viewed webhook fires when a non-owner read session ends | Free |
| New Download | Webhook | Fires when a reader saves your PDF to disk. Your own downloads as the owner never fire it | Free |
| New Form Fill | Webhook | Fires when a reader completes an email gate or lead-capture form on your document | Pro |
| Link Expired / Self-Destructed | Webhook | Fires when a document link self-destructs after reaching its view limit | Free |
| New Reader Comment | Webhook | Fires when a reader leaves a feedback note on your document | Free |
| Receipt Confirmed | Webhook | Fires when a reader confirms receipt of your document | Free |
The polling trigger (New Document Read) checks for new reads at Zapier's standard interval, walking the events feed with a stored cursor. Webhook triggers fire instantly. EveryPage attempts each delivery up to 5 times (1 minute, 10 minutes, then hourly backoff) before abandoning it; see webhooks for the full retry and auto-disable policy.
Webhook triggers are powered by EveryPage webhooks, which are available on all plans. Only the form-fill trigger carries a plan requirement: your account must be on Pro at the time the event fires—upgrading later does not retroactively fire past events.
Deliveries are signed with X-Everypage-Signature. The Zapier app verifies the signature and rejects mismatches whenever Zapier hands it the raw request bytes; where the raw body is not available it accepts the delivery rather than dropping it.
Actions
Actions perform work on your behalf—they upload documents, modify settings, or create variants. Unless otherwise noted, actions are available to all plan tiers.
| Action | Description | Pro feature |
|---|---|---|
| Upload PDF & Get Tracking Link | Uploads a PDF to EveryPage and returns a ready-to-share link | — |
| Update File Settings | Modifies an existing document's sharing settings (passcode, expiry, download permission, viewer mode, and more) | Some fields |
| Create Link Variant | Mints a per-recipient tracked link, attributing readership to that recipient | Yes |
| Replace Content | Swaps the PDF behind an existing share link—the link, QR code, settings, and analytics all survive | Yes |
| Delete File | Moves a document to trash (see the note below—the action's own description overstates this) | — |
When you update file settings, you can set only the fields you need to change—omitted settings keep their current value. This is useful for workflows like "when a CRM deal closes, expire the proposal link."
The Zapier app builds its share link, QR code URL, and embed code from the document's UUID rather than its short ID. Both forms resolve to the same document; the Make and n8n apps prefer the short ID. The QR URL is the public, unauthenticated /api/files/{uuid}/qr-code path so downstream apps can render it without an EveryPage key.
Create Link Variant
Creating link variants is a Pro-only feature. Each variant receives its own short link and optional recipient label, so you can send individual links to each recipient and track them separately. Variants also support optional per-recipient overrides for download permission and page range (allowDownload, pageFrom, pageTo); the overrides object replaces the variant's existing overrides wholesale rather than merging into them.
Zapier offers Create only. Listing, updating, revoking, and deleting variants are not available as Zapier actions—use the Make or n8n apps, the API, or the EveryPage dashboard.
Replace Content
Content replacement is Pro-only and is the primary way to un-burn a link. When you replace a document's PDF, the share URL, QR code, and all readership history remain intact—only the bytes change. This is useful for workflows like "new version uploaded to Drive → automatically update the shared link without losing the history."
Delete File
The action's own description in Zapier says it "PERMANENTLY deletes," but it sends a plain DELETE, which the API soft-trashes. On Basic and Pro the document lands in trash and stays restorable (7 days on Basic, 30 on Pro); on Free, which has no trash, the delete is immediate and permanent. There is no purge option on the Zapier action. See trash and recovery.
Searches
Searches retrieve information about a single document or pull readership data.
| Search | Description |
|---|---|
| Find File | Locates a document by file name (case-insensitive substring match). Returns the document's UUID, short ID, size, page count, viewer mode, and share link. |
| Get Analytics Summary | Fetches a document's readership report: total views, sessions, unique readers, countries, average time spent, downloads, completion rate, and active readers. |
The analytics summary response includes a tier field naming the plan the report was built at. The API omits sections above your tier, so those fields come back empty: median read time and completion rate need Basic, and active readers, new sessions, and returning sessions need Pro.
Important details
Form fill requires Pro at event time
The "New Form Fill" trigger fires when a reader completes an email gate or lead-capture form. Because the payload carries captured lead data, EveryPage only delivers gate.completed while the account is on Pro at the moment of the event. Rather than let you turn on a Zap that would silently never fire, the app checks your plan when you enable the Zap and refuses with an upgrade prompt if you are below Pro.
Webhooks and availability
Zapier webhook triggers rely on EveryPage webhooks under the hood. Webhooks are available on all plans and do not require a Pro account—only gate.completed (the New Form Fill trigger) carries a plan requirement. Turning a Zap on registers the webhook subscription; turning it off deletes it.
Related
- API keys — create and manage your API keys
- Webhooks — how event delivery and retries work
- Events feed — the data structures for views, downloads, and captured leads
- Link variants — creating and managing per-recipient tracked links
- Trash and recovery — how soft delete and permanent purge work
- Plans and limits — tier requirements and API rate limits