Substack New Subscriber Email Has No Address? What Changed

The problem

"Usually it shows the person’s email and profile. But now it’s just a general email of “1 person has subscribed to your Substack”. It asks you to visit your dashboard for more details." (r/Substack, 20 March 2026)

"Then one fine day Substack quietly removed subscriber email addresses from notification emails. No announcement. No deprecation period." (GenAI Unplugged, April 2026)

Getting subscriber events out of Substack is one of the most common integration complaints. In our review of public Reddit, X and forum posts (October 2026), it appeared in 19 coded forum sources and 20 distinct social sources. In the social posts, operators and agencies raised it more than any other theme. Many of those people had built on the notification email: a 2022 r/Substack thread explained the Gmail-to-Zapier trick, a Make community post piped a Gmail folder into ActiveCampaign, and a Zapier community thread fought spam filters on the parser address. As GenAI Unplugged put it: "Thousands of Substack creators built the same workaround."

This guide covers what changed, what still shows you who subscribed, and how to replace the broken automations, as of October 2026.

What changed in Substack's new subscriber notification?

	Before mid-March 2026	After (reports from 20 March 2026)
Free subscriber email	The person's email and profile	"1 person has subscribed to your Substack"
Next step	Read it in the email	"visit your dashboard for more details"
Gmail/Zapier parsing	Worked: split text, extract email	Nothing to extract
Announcement	—	None found

The setting itself still exists. Substack's help centre describes New free subscriber: "you'll be notified by email and see an Activity notification about new subscribers" (help). The earliest report we found, on 20 March 2026, says the change appeared "in the last couple of days" (r/Substack). An April 2026 write-up describes notifications that had "a name but no email address you could parse" (GenAI Unplugged).

We haven't confirmed what paid-subscriber or cancellation notifications contain today. The "Canceled free subscription" setting is still documented as "an email confirmation that their email has been disabled and removed from your list" (help).

Where can I still see who subscribed?

1. The Subscribers dashboard. Open Subscribers, add columns with Display, and "click any column's header to order your subscriber list by that column" (dashboard help). A saved segment such as "free subscribers who signed up after March 1, 2026" (Substack's own example) updates automatically as people join.
2. The CSV export. Subscribers → All subscribers → the three dots → Export. "Visible columns only" includes "the date someone subscribed and their type of plan"; you can also tick specific people and export just them (export help). Names aren't included.
3. Tags. Tag batches you import or segment, so the export can be filtered later (tags help).
4. The Publisher API, if your publication has it. According to the open-source substack-publisher-mcp wrapper, the read-only Publisher API can return daily subscriber counts and "look up a subscriber by email". It can't list subscribers, and the README warns it "may not be enabled for your publication yet".

Which workflows broke, and what replaces them?

Workflow that broke	Why	Replacement
Gmail filter → Zapier/Make → Kit, Bento, ActiveCampaign	The email address is gone from the body	Weekly export diff, imported to the other tool (see below)
"New subscriber" welcome drip in another ESP	No address to trigger on	Send the drip from Substack's own welcome email, or invite readers to opt in to the drip
Gmail → enrichment (Clay, Apollo)	No address	Export, then enrich in batches, if your privacy notice allows it
Slack or Discord "new subscriber" ping	Still works as a count	Keep it as a ping that says "someone subscribed", with no identity
Paid-subscriber alerts	Unknown	Your own Stripe account sees paid subscriptions (see Stripe vs Substack numbers)

The weekly export diff, step by step:

1. Once a week, export the subscriber list with visible columns, or export a segment filtered by start date.
2. Keep last week's file. New rows are emails in this week's file that weren't in last week's; missing rows are people who left.
3. Import the new rows into Kit or your CRM, but only into a list where they've agreed to be emailed (see the consent note below).
4. Mark the date. One writer who automated a similar weekly sync explained why it matters: "It's the people who slipped through the weeks I forgot." (Prisca Onyebuchi, LinkedIn)

For new readers who arrive through your own website, there's a cleaner route. Collect the email on your own form with a clear "subscribe to my Substack newsletter" line, then hand the reader to Substack's /subscribe page. You know the address because the reader gave it to you, not because you parsed Substack's email.

If you want event-style triggers, our guide to Substack webhooks covers what exists and what doesn't. Full sync options are in syncing Substack to Kit or HubSpot.

What about consent when I copy new subscribers elsewhere?

A reader who subscribed on Substack agreed to your Substack newsletter. A 2022 commenter's advice on the Gmail hack still applies: "Bear in mind that they didn't express consent to receive emails from your CRM" (r/Substack). Tell people in your welcome email what else you'll send and how to opt out, or invite them to join the second list themselves.

What not to do

• Don't scrape the dashboard with a script or a hosted browser that logs in as you to rebuild the old notification. Substack's Terms of Use prohibit crawling or scraping any part of Substack, including "through use of manual or automated means".
• Don't reuse session cookies in Zapier, Make or n8n to call Substack's internal endpoints.
• Don't add new Substack subscribers to marketing sequences they never agreed to.

Is there a tool for this?

newsletterapi offers subscriber analytics from your own exports: upload or forward a weekly export and get a dated diff of new, upgraded and lost subscribers that agents can read through our MCP server. It works only from data you export yourself.