Scribe Webhooks
Real-time email signature events

Your tools hear about it the moment something happens in Scribe: a new conversion, a signature that fails to install, a teammate who joins, a campaign that goes live. Connect Zapier, Make, n8n, or your own systems in minutes.

Ask your AI agent to help you set up Scribe Webhooks

Connect Scribe with your AI agent

Copy prompt

I want to receive Scribe (https://www.scribe-mail.com) webhooks, the real-time events from my email signature workspace. Walk me through it step by step. Read the docs at https://help.scribe-mail.com/webhooks/overview and the event catalog at https://help.scribe-mail.com/webhooks/events. Then help me pick the events I need, build an HTTPS endpoint that verifies the Svix signature and answers with a 2xx within 15 seconds, and register it in Scribe under Settings, Webhooks, Manage webhooks. If I don't have a Scribe account yet, send me to https://www.scribe-mail.com to start a free 14-day trial first. Send a test delivery from the webhook portal and show me the payload so I can confirm it worked.

Use cases

What you can build with Scribe Webhooks

Each event reaches your endpoint seconds after it happens, so signature data flows into your CRM, ad platforms, and IT tools without a nightly sync.

Attribute revenue in your CRM

Push signature-attributed conversions into your CRM or warehouse as they happen, with the teammate, template, and campaign that earned them.

Retarget engaged visitors

Feed Google Ads and Meta audiences with people who clicked an email signature, and suppress them once they convert.

Alert on broken installs

Tell IT the moment a signature fails to install in a mailbox, with the error code and the mailbox that needs attention.

Repair integrations fast

Catch a revoked Google Workspace or Microsoft 365 connection before signatures go stale, and send an admin straight to the reconnect screen.

Automate onboarding

Mirror teammate arrivals and departures into your ITSM, HR tool, or internal directory without a nightly sync.

Coordinate campaigns

Announce a banner going live in Slack, and mark the exact start and end times on your analytics dashboards.

Keep an audit trail

Subscribe one endpoint to every event and archive each payload with its timestamp: who published which signature, which integrations were connected or removed, when each teammate arrived and left. Answer compliance questions months later.

How it works

Live in three steps

Set up an endpoint once from the dashboard. Scribe signs every delivery, retries failures for about a day, and keeps a log you can replay.

1

Add your endpoint

In Settings, open Webhooks and click Manage webhooks. Add any HTTPS URL: your own server, or a catch hook from Zapier, Make, or n8n.

2

Pick your events

Subscribe the endpoint to the event types it needs, or to all of them. Send a test delivery to see the payload before real traffic arrives.

3

Verify and act

Every event is signed, so you know it came from Scribe. Confirm receipt within 15 seconds, then let your workflow do the rest.

Events

Every event your stack can react to

Events fire on state changes, not on every write, so each delivery means something actually happened. Every payload carries its type, a timestamp, and the same IDs as the REST API.

conversion.recorded
A conversion is attributed to a signature click, with its value, currency, and the teammate, template, and campaign behind it.
visitor.identified
A visitor who came from a signature is identified for the first time.
signature.published
A signature or one of its variants is published and goes live.
signature.installation.failed
A signature fails to install in a mailbox. Fires once per failure, not every day while it stays broken.
teammate.created
A teammate is added from the dashboard, the API, or a directory sync.
teammate.deleted
A teammate is removed, with their identifiers in the payload one last time.
campaign.*
One event for each step of a banner campaign: scheduled, started, paused, resumed, and ended.
integration.connected
An integration is connected and becomes active for the first time.
integration.access_lost
Scribe loses access to an integration. The payload links straight to the reconnect screen.
integration.disconnected
An integration is removed by a user.

FAQ

Your Scribe Webhooks questions answered

Scribe webhooks send a signed HTTPS POST request to your endpoint every time something happens in your email signature workspace: a conversion is recorded, a visitor is identified, a signature is published or fails to install, a teammate is added or removed, a campaign changes state, or an integration is connected or loses access. You react to events instead of polling the API.

conversion.recorded, visitor.identified, signature.published, signature.installation.failed, teammate.created, teammate.deleted, campaign.scheduled, campaign.started, campaign.paused, campaign.resumed, campaign.ended, integration.connected, integration.access_lost, and integration.disconnected. Subscribe each endpoint to the events it needs, or to all of them.

In the Scribe dashboard, open Settings, then Webhooks, and click Manage webhooks. Add your HTTPS endpoint URL, pick the event types, and send a test delivery. The same portal shows delivery logs, replays failed deliveries, and rotates signing secrets.

No. Any HTTPS URL works, including the catch hook URL from Zapier, Make, or n8n. Build your own endpoint when you need signature verification and full control over retries, which anything that writes to a system of record deserves.

Every delivery carries svix-id, svix-timestamp, and svix-signature headers. Scribe webhooks are powered by Svix and follow the Standard Webhooks signing scheme, so an official Svix library verifies them in one call with the signing secret shown in the webhook portal.

Nothing is lost. Failed deliveries are retried automatically with exponential backoff for about a day. Once your endpoint is healthy, replay the missed deliveries from the webhook portal. Delivery is at least once, so deduplicate on the svix-id header.

Webhooks are part of the Scribe API, included in the Business and Enterprise plans and in the 14-day free trial. Workspace owners and admins manage the endpoints.

ROI

Calculate your potential revenue
and savings

See how much revenue and time your team could gain with Scribe email signatures.

12% average click-through rate - 6x higher than email marketing standards. Measured on 50,000+ emails with Scribe marketing banners.

With Scribe's conversion tracking, it's a number you will be able to measure.

ROI Calculation

Monthly

Yearly

Save 20%

252,0000

Yearly outreach emails

New leads per year

30,2400

Paying customers

6000

Average order value

$100$0

Potential yearly revenue

$60,000$0

Yearly billing discount

-$348$0

Scribe Yearly Cost

-$1,392$0

Total Earned

+$58,608$0

This is earned back on a yearly basis

Stripe email signature – Patrick Collison
Notion email signature – Camille Ricketts

Start your 14-day
free trial

Join 10,000+ companies using Scribe to power 15 million daily brand impressions

No card required. All features. Unlimited users.

Nike email signature – Greg Hoffman
Headspace email signature – Andy Puddicombe