Search your own problem
SolvedReceipt · Shared by the builderReceipt no. 6375
What was broken

to and in a weekly newsletter without copy-pasting.

Building it all on the n8n canvas is where automations get fragile: business rules hidden in expressions, retries that email someone twice, long jobs that time out halfway.

What they built

Self-hosted n8n with a strict split. The Next.js app owns every decision and all the data; n8n owns the schedule and the integrations. A 12-hour schedule drafts the next post from a topic backlog, a webhook cross-posts each published post to dev.to with a canonical link back, and a weekly loop sends the newsletter in resumable batches so a stopped run never mails anyone twice. A person still reviews and publishes every post.

What changed
136 posts published since June 2026 (133 drafted by the pipeline), 80 cross-posted to dev.to with a canonical link.
Time to results
Under 4 weeks
Company size
1-50 people
Project cost
Under $25K
Runs on
Other
More solutions like this

See all 38 solutions for marketing teams

Proof of Work, weekly

New solutions every week, and the case studies behind them.

Our newsletter. What got built, what it changed, who did it. No pitches.