Substack n8n: What You Can Automate in 2026

n8n is where many writers and operators wire their content pipeline together, and Substack is usually the one platform with no node. This guide shows what n8n can do around a Substack publication today using official surfaces only, what the community Substack node does and the risks it carries, and where the honest boundary is: n8n can trigger, read, draft and schedule Notes, but it can't publish a long-form post for you. Facts are as of October 2026. For the full map of Substack's developer surfaces, start with our Substack API guide.

newsletterapi is an independent project, not affiliated with Substack. Nothing below depends on newsletterapi.

The problem

The ask is simple: treat Substack like every other destination in the workflow. One builder put the blocker plainly in r/n8n: "Problem: Substack doesn't provide a public API on my plan." (Reddit). Others went around it, for example to "automate Substack Notes publishing through a custom node connected to Substack's private API" (LinkedIn). In the n8n community thread for the Substack community node, several users report 403 Forbidden errors on its Create Note operation, and one ends: "I have not yet, gave up so vibe-coded my Chrome Extension." (n8n Community). An operator elsewhere summed up the browser-automation route: "agree, browser automation for this stuff feels like a ticking time bomb" (r/MarketingAutomation).

The practical answer is to automate everything around the publish button, with sources Substack supports.

What can n8n do with Substack?

Job	n8n nodes	Substack surface	Status
Run a workflow when you publish	RSS Feed Trigger	Public RSS feed	Works today, no login
Read recent posts as data	RSS Read	Public RSS feed	Works; paid posts cut at the paywall
Draft a post or Note in your voice	RSS Read, Code, Basic LLM Chain or AI Agent	Your feed as examples	Works; output is a draft for you
Post stats and daily subscriber counts	HTTP Request with Header auth	Publisher API	Only where Substack has enabled it
Schedule a Note	HTTP Request to Buffer	Buffer's Substack integration	Works through Buffer
Process your subscriber or post export	Google Drive, Extract From File	Your own export	Works; you download the export
Publish or schedule a long-form post	none	No official write API	Not possible officially

Is there a Substack node for n8n?

Not an official one. n8n's integrations page for Substack (n8n.io/integrations/substack) returned 404 when we checked on 2026-10-24. What exists are community packages on npm, both by the same author:

• n8n-nodes-substack reads profiles, posts, Notes and comments and can create Notes. Its credential takes your publication address and an "API Key", which in the community thread turns out to be a session cookie copied from your browser. The README now says it "is superseded" and "no longer actively developed". It had 36 npm downloads in the month to 2026-10-22 (npm downloads API).
• n8n-nodes-substack-new talks to a self-hosted "Substack Gateway" rather than to Substack directly. Its README says: "This is an unofficial community node. It is not part of n8n and is not compatible with n8n Cloud."

Before you install either, read n8n's own community node risks: community nodes "have full access to the machine that n8n runs on", "any community node that you use has access to data in your workflows", and authors "may introduce breaking changes". n8n also says unverified community nodes "aren't available on n8n cloud and require self-hosting" (installation docs).

The Substack side matters too. Both packages act as you on undocumented endpoints, and Substack's Terms of Use forbid anything that "Jeopardizes the security of your Substack account", "such as allowing someone else to log into Substack as you". If a session cookie leaks from a workflow, it is your account. Our guide to the Substack API 403 error explains why these calls fail from servers.

Workflow 1: do something every time you publish

This is the most reliable Substack automation in n8n, because it only reads your public feed.

1. Add an RSS Feed Trigger node. Set Feed URL to https://yourname.substack.com/feed (or https://yourdomain.com/feed); every publication has one, per Substack's help centre. Under Poll Times, choose Every Hour or Every X (n8n docs).
2. Add the action: a Slack or Discord message, a Google Sheets "Append Row" to log every post, or a draft for LinkedIn. Map {{ $json.title }}, {{ $json.link }}, {{ $json.isoDate }} and {{ $json.contentSnippet }}.
3. Activate the workflow.

You won't flood a channel with old posts. In n8n's trigger source, the node remembers the newest item date it has seen and only emits items published after it; on first activation it starts from the current time, and a manual test run returns just the newest item. For the full Slack and Discord build, including a code version, see Substack to Slack.

Workflow 2: draft in your voice with AI

n8n is good at the part before publishing: turning notes, transcripts or links into a first draft that sounds like you. The trick is to feed the model your own recent posts as examples.

1. Start with a Schedule Trigger, a Form or a Webhook that receives your notes.
2. Add RSS Read with your feed URL (n8n docs).
3. Add a Code node in its default "Run Once for All Items" mode (n8n docs) to turn the latest posts into style examples:

// Code node after RSS Read on your own feed (mode: Run Once for All Items)
const examples = $input.all().slice(0, 5).map(({ json }) =>
  `TITLE: ${json.title}\nDATE: ${json.isoDate}\nOPENING: ${(json.contentSnippet ?? "").slice(0, 600)}`
);
return [{ json: { examples: examples.join("\n\n---\n\n") } }];

4. Add a Basic LLM Chain (or AI Agent) with your model credential (n8n docs). In the prompt, reference {{ $json.examples }} and your notes, and ask for Markdown with a title, subtitle and body.
5. Send the result somewhere you'll review it: a Google Doc, an email to yourself, or a Notion page.

Then paste it into the Substack editor and schedule it there. We tested the Code node logic against a live Substack feed on 2026-10-24. Our Markdown to Substack guide covers the paste step without losing formatting.

Workflow 3: pull stats from the Publisher API

If Substack has enabled the read-only Publisher API for your publication, an HTTP Request node can read it. Create a Header auth credential (n8n docs) with name authorization and your key as the value (no Bearer prefix), then call GET https://publisher-api.substack.com/v1/subscribers/counts?startDate=2026-10-01. The paths and fields come from the open-source substack-publisher-mcp wrapper and are self-reported by its author: daily rows with total_email_subscribers and paid_subscribers, newest first, plus /posts and /posts/{urlSlug}/stats for per-post opens and new subscribers. Append the rows to Google Sheets for a growth chart; our Google Sheets dashboard guide has the sheet layout. To check whether you have a key, see Substack API key.

Workflow 4: schedule Notes through Buffer

Buffer is the official route for Notes. Its help centre says "Buffer publishes Substack Notes" and that "Substack Notes can be created, scheduled, and measured through Buffer's API and MCP server" (Buffer Help). Connect your Substack in Buffer, then use an n8n HTTP Request node to queue a Note through Buffer's API, for example a short teaser built from Workflow 1 each time a post goes out. Buffer notes the limits: Notes publish as plain text, and "Buffer doesn't publish long-form Substack posts or newsletter issues." More on Notes in our Substack Notes guide.

For the same jobs in Zapier, Make, IFTTT and other tools, see what works for Substack integrations.

Can n8n publish a post to Substack?

Not through any official route, as of October 2026. The Publisher API is read-only, and Substack's own MCP server help page says it "cannot publish posts, send Notes, or modify your account" (Substack help). Tools that do publish sign in as you, which carries the account and terms risks above. Our recommendation: let n8n do everything up to a reviewed draft, then paste and schedule it in Substack yourself.

How does newsletterapi fit into n8n?

newsletterapi gives n8n cleaner inputs. The embeds post.published webhook can call an n8n Webhook node with a signed payload when a new post appears in your feed, instead of polling. The Posts API returns any post, including paid posts from the export you upload, as Markdown or JSON for an HTTP Request node. For drafting, our MCP server exposes your archive and a style guide to an n8n AI Agent through n8n's MCP Client node. Nothing is published on your behalf. To get access, see pricing or email hello@newsletterapi.io.