Does Substack Have Webhooks? What to Use Instead

The problem

"substack doesn't use webhooks." — @Ace_theSage on X, 21 October 2026

"Any ideas on how to sync Unsubscribes between Substack and the crm?" — r/Substack

If you run a CRM, an email course, a Slack channel or an ad account next to your newsletter, you want Substack to tell those tools when something happens. It doesn't. In our review of public Reddit, X, Hacker News and GitHub posts (October 2026), 19 forum, review and GitHub sources and 20 separate social posts asked for some form of "subscriber events out": new subscribers, upgrades, cancellations or unsubscribes sent to another tool. Examples include an agency asked to unsubscribe people in GoHighLevel when they leave Substack and a long-running r/Substack thread on CRM sync.

This guide says what exists as of October 2026, what each signal can and can't tell you, and how to build honest "post published" and "new subscriber" automations without putting your account at risk.

Does Substack have webhooks in 2026?

No. We checked three ways on 21 October 2026:

• Help centre. We searched the public articles in Substack's help centre for "webhook", "Zapier" and "integrations". None describes a webhook setting. The Analytics settings article lists the only outbound tools: Google Analytics, Google Tag Manager, the Meta and X pixels and Parse.ly.
• Automation directories. zapier.com/apps/substack/integrations returns a 404. IFTTT has a Substack service with two triggers (new post, new Note) and no actions.
• Official APIs. The Publisher API, where it is enabled, is pull-only: you ask it questions, it never calls you. Its endpoints, described by the open-source wrapper dkships/substack-publisher-mcp, cover posts, post stats, daily subscriber counts and a single-email lookup.

So any "Substack webhook" you build is really one of the substitutes below. For the full map of official surfaces, see does Substack have an API.

Which signal should I use for each event?

Event	Best available signal	Who it identifies	Typical latency
New post published	RSS feed at /feed, read by any RSS trigger or IFTTT "New post by user"	The post	5 minutes (IFTTT paid) to 1 hour (IFTTT free)
New Note	IFTTT "New note by user"	The Note	5 minutes to 1 hour
New free subscriber	GA4 or Tag Manager sign_up event	Anonymous (no email)	Seconds
New free subscriber (with email)	Subscriber CSV export, diffed against the last one	Email, date, plan	As often as you export
New paid subscriber	Webhook from your own Stripe account	Email, plan, amount	Seconds
Cancellation or failed payment	Stripe webhook	Email	Seconds
Free unsubscribe	Export diff (the address disappears)	Email	As often as you export
Daily net growth	Publisher API daily counts (if enabled)	Counts only	Daily
"Someone subscribed" ping	Substack's notification email	Count only	Minutes

The polling times come from IFTTT's Substack page. The rest of this page explains each row.

How do I trigger something when I publish a post?

Use RSS. Every publication has a feed at https://yourname.substack.com/feed (Substack help). Any automation tool with an RSS trigger can watch it:

1. Copy your feed URL. Use the custom-domain version if you have one.
2. In your tool (IFTTT, Zapier, Make or n8n), add an RSS "new item" trigger with that URL.
3. Map the item's title, link and description to the action you want: post to Slack, add a row to a sheet, send to your CMS.
4. Test it with a published post before you rely on it, and check how your tool handles paid-only posts.

IFTTT's own Substack trigger does the same job and polls every 5 minutes on Pro and hourly on Free. Narrareach, a paid third-party tool, advertises webhooks when a Note is published or updated; its page does not mention subscriber events.

How do I get a "new subscriber" event?

There is no single answer, because Substack splits subscribers across several systems. Combine these.

Paid subscribers: use your own Stripe account

Substack's paid subscriptions run through a Stripe account the writer owns. In your Stripe Dashboard you can add a webhook endpoint (Stripe docs) and listen for customer.subscription.created, customer.subscription.updated, customer.subscription.deleted, invoice.payment_failed and charge.refunded. Use a restricted key with read permissions only if a tool needs API access.

Know the blind spots:

• iOS in-app subscriptions are paid to Apple, and Apple pays Substack in monthly batches, so there is no per-subscriber Stripe event (Substack help).
• Gift subscriptions: the Stripe customer is the buyer, while the recipient shows as "gift" in Substack (Substack help).
• Comps create no charge at all.

Never create charges, subscriptions or refunds in Stripe from an automation. Substack's Publisher Agreement says you must process reader payments "only in the manner determined by us". Read-only is the safe line.

Free subscribers: exports, counts and your own forms

• Export diff. The Subscribers page exports a CSV with the date someone subscribed and their plan, and Settings → Exports builds a full zip (Substack help). Export weekly, compare with last week, and you have email-level "new" and "gone" events. Latency equals how often you export.
• Counts. If your publication has the Publisher API, its daily counts give net new free and paid subscribers per day, with no identities.
• Your own forms. If the reader signs up on a form you run, you hold the email and consent the moment they click. Hand them on to Substack's subscribe page so they opt in there too.
• Notification email. The "New free subscriber" setting sends an email and an Activity notification (Substack help). Writers reported in March 2026 that it now says "1 person has subscribed" without the address. More on that in new subscriber notification with no email.

Anonymous events: Google Analytics and Tag Manager

Substack loads your GA4 tag and fires events for "page views, sign ups, and paid subscriptions" (Substack help). These are good for attribution (which page or campaign drove the sign-up) but carry no email. In Substack's public page code (observed October 2026), Tag Manager allows Google-built tags only by default, so a custom HTML tag that calls your webhook will not fire on most publications.

What should I not do?

• Don't give a cloud tool your Substack login or session. The Terms of Use ban "allowing someone else to log into Substack as you" and processes that run "while you are not logged into Substack".
• Don't scrape your dashboard from a server on a schedule. The same terms ban crawling "through use of manual or automated means".
• Don't rely on parsing notification emails for addresses. The format has already changed once without notice.
• Don't push Substack subscribers into another email tool and mail them without their consent. They opted in to your Substack. See syncing Substack subscribers to Kit or HubSpot for consent-safe patterns.
• Don't write to Stripe. Read-only keys and webhooks only.

Where newsletterapi fits

newsletterapi is a read-only layer for Substack writers, including website embeds with content webhooks that fire when you publish, and subscriber analytics from your export. If you want them, get access. Without them, RSS plus your own Stripe webhooks plus a weekly export covers most of what people ask for, without any grey routes. For the wider picture of what connects to Substack, see Substack integrations.