Post

Tamilore, our Senior Content Creator, posted a Substack Note every day in September for The Weekly Scroll, Buffer's own publication. She batch-wrote most of them and scheduled them ahead. Here's how scheduling Notes works, and what a month of it taught her. 🧡

First, yes, you can schedule Substack Notes, and there are two free ways to do it. Substack added a scheduler to its own composer, and Buffer's Substack integration is built on Substack's official API, in partnership with Substack.

Inside Substack on the web, write your Note, click the calendar icon at the bottom, pick a date and time (it uses your local timezone), then Save and Schedule. The Note sits in your Drafts with its publish time showing. You can schedule up to three months ahead.

On mobile, the same option lives in the three-dot menu when you're writing a Note. Tap it and choose Schedule.

There are a few things the native scheduler doesn't do. There's no calendar view, so your scheduled Notes sit in a list of drafts. You schedule one Note at a time. The Note only goes to Substack. And per-Note reporting stops at likes, replies, and restacks.

Scheduling through Buffer covers those gaps. Connect Substack as a channel, write the Note, and pick a time. To send the same Note to LinkedIn, Threads, X, or Bluesky, select those channels in the same post. Once it's live, you'll see impressions, engagement, follows, and subscriber conversions!

Now the lessons! Tamilore's first is to batch-write most of the week's Notes in one session, and leave a few slots open for the spontaneous replies and restacks.

The second is to schedule for when your readers are active, whatever time you happen to be writing. The third is to keep a running list of Note ideas. She keeps hers in Buffer's Ideas and pulls from it when she sits down to write. πŸ‘€

Two answers from the FAQ: Scheduled Notes don't perform worse than ones posted live, since timing and engagement matter more. And neither Substack nor Buffer can schedule a restack or a reply, so those stay manual. πŸ’™

No replies yet.