Free plan

Slack

Post Block Kit messages to Slack when documents are viewed, downloaded, or gates are completed.

There is no EveryPage Slack app. Slack support is a format option on an outgoing webhook: you provide a Slack Incoming Webhook URL, add it as an EveryPage webhook, and choose the Slack format. EveryPage then posts Block Kit messages to that channel. There is no slash command, no link unfurling, and no Slack App Directory listing.

Setup

  1. In Slack, create an Incoming Webhook for the channel you want EveryPage messages in, and copy its URL. Slack's own documentation covers the current steps.
  2. In EveryPage, go to Account → Webhooks → Add webhook
  3. Paste the Slack webhook URL into the Endpoint URL field
  4. Choose the Slack format (not JSON)
  5. Select which events trigger messages
  6. Click Add webhook

The endpoint URL must be HTTPS, and it may not resolve to a private or loopback address.

For the full webhook reference—including test endpoints, other formats, and how to configure per-file webhooks—see Webhooks reference.

Events and messages

Every event type produces a formatted message with:

  • A header stating the event (e.g., "Document viewed", "Gate completed - new contact")
  • A fields section: the document name first, then the event's remaining payload keys in alphabetical order, with camelCase keys relabelled ("pagesViewed" becomes "Pages viewed")
  • A link to the document's readership page, when the event payload carries a file identifier

Available events:

  • Document viewed — a non-owner's reading session ended
  • Document downloaded — a non-owner explicitly saved a copy
  • Gate completed — a reader passed an email or lead-capture gate (Pro at event time)
  • New feedback note — a viewer left a public note on the document
  • Receipt confirmed — a reader confirmed receipt of the document
  • Document burned (view limit reached) — the view limit was reached and the blob was destroyed
  • Document content replaced — the owner swapped the document's content in place
  • Invite opened — an email invitee opened the document for the first time
  • New proofing feedback — a viewer left their first page mark or annotation
  • Test event from EveryPage — sent when you click "Send test" on the webhook

Signing and security

Slack Incoming Webhook URLs authenticate by URL alone—the URL itself is the secret. Because of this, Slack-format deliveries are deliberately unsigned. Unlike the JSON format, which carries an X-Everypage-Signature header for verification, Slack messages have no HMAC signature: possession of the URL is what Slack accepts as proof, so an additional signature would add nothing Slack can check.

Creating a Slack-format webhook therefore does not show you a signing secret, as the JSON format does.

If you need signed delivery for security auditing or compliance, use the JSON format instead and verify the signature at your endpoint.

Text and rendering

Message text is escaped for Slack's markup syntax (ampersands, angle brackets), so file names and user-provided text render safely. Field values are rendered as plain text in Slack's block syntax. Slack caps a section at 10 fields, so EveryPage sends at most 10 and drops any remaining payload keys.

Reliability and retries

Webhooks are delivered with retry and backoff:

  • First attempt: immediate
  • Failed attempts: retry on a fixed backoff schedule
    • After the 1st failure: wait 1 minute
    • After the 2nd failure: wait 10 minutes
    • After the 3rd and subsequent failures: wait 1 hour
  • Max attempts: 5, after which the delivery is abandoned
  • Auto-disable: after 20 consecutive abandoned deliveries (each having used all 5 attempts), the webhook is switched off and you receive an email

Any successful delivery resets the failure counter. A webhook that has been auto-disabled cannot be switched back on: delete it and add it again once the endpoint is fixed. Sending a test does not re-enable it.

Limitations

  • Your own actions never fire events. If you (the owner) view your own document or complete a gate on it, EveryPage does not send a webhook message.
  • There is no Slack OAuth flow. You must create an Incoming Webhook URL directly in Slack and paste it here.
  • A webhook cannot be edited after creation. Changing the URL, the format or the event list means deleting it and adding a new one.
  • An account may hold 25 webhooks.

Plans

Webhooks are available on every plan, Slack format included. The single exception is gate.completed: those deliveries require Pro at the moment the event occurs, because their payload carries captured lead data. On Free and Basic the event is recorded but no Slack message is sent.