The lesson
State what changed in your thinking and why the reader should care, without withholding the whole idea.
Give every issue more than one chance to travel.
Watch your public publication feed, find several useful angles inside each new issue, and build a reviewable sharing queue instead of one repetitive announcement.
Paste the public URL. Keep your Substack login to yourself.
Every Substack publication has a feed at its publication domain followed by /feed. Emelyn reads that public feed, so this workflow does not ask for your Substack password or pretend there is a publishing API connection.
Public issues onlyThe feed is the boundary. Private drafts, subscriber emails, audience lists, and unpublished Notes are not fetched.
{
"publication_url": "https://your-publication.substack.com",
"feed_url": "https://your-publication.substack.com/feed",
"check_every_minutes": 15,
"new_issue_action": "prepare_7_day_campaign",
"angles": ["lesson", "surprising_quote", "practical_takeaway"],
"channels": ["linkedin", "threads", "instagram"],
"review_required": true,
"dedupe_by": ["guid", "canonical_url"]
}Publication recipe revision 1.0 · Substack publication RSS · Last tested 29 August 2026.
Do not spend a week repeating “new issue out now.”
The first useful job is choosing what the issue contains that deserves its own conversation. Emelyn proposes angles and shows the supporting passage before drafting.
The surprising line
Use a short, attributable passage as the start of a conversation—not as empty quote-card decoration.
The practical takeaway
Turn one method or decision into something a reader can apply before they click.
The feed supplies the issue. The campaign supplies the sequence.
Each public item becomes one source record. Its fields stay attached while Emelyn creates a seven-day queue with different angles, formats, and posting times for the channels you chose.
| Substack feed | Emelyn | Use |
|---|---|---|
| guid | substack.issue_id | Saves the issue identity |
| link | source_url | Keeps the public issue as the destination |
| title | source_title | Names the subject; not copied into every caption |
| description or content | source_text | Supplies the public excerpt or body available in the feed |
| pubDate | source_published_at | Starts the sharing window |
| enclosure | source_media | Uses the issue image when the feed provides one |
Seven-day output
- Day 1: the clearest lesson in the issue
- Day 2: a question raised by the argument
- Day 3: a visual summary or carousel brief
- Day 4: a behind-the-decision detail
- Day 5: the surprising line with context
- Day 6: a practical takeaway
- Day 7: a final angle for readers who missed it
This is a starting sequence. Review, remove, or reschedule any draft before publishing.
The feed can tell us an issue exists. It cannot tell us everything.
The connection makes its intake state visible and stops safely when the publication or item cannot be read.
Same GUID or URL
Ignore the repeat and keep the existing campaign. A feed reorder is not a new issue.
Feed unavailable
Back off and retry. Keep the last checkpoint; do not mark old issues as new.
Excerpt only
Draft only from the public text returned. Never invent the hidden part of a paid issue.
Issue removed
Flag the campaign and destination link for review. Do not keep scheduling promotion blindly.
What this does not do: publish Substack Notes, read subscriber data, alter your publication, open paid content, guarantee a feed refresh time, or turn every issue into the same captions. The source must be yours or one you are allowed to repurpose.
A workflow for writers, not another auto-post switch.
Substack writers ask for a setup that notices new issues, lets them customize the caption, spaces promotion over time, and preserves their voice. The connection uses Substack’s documented publication feed and keeps private account data out of scope.