Automation library · Content

Cross-post newsletter issues to Bluesky, Telegram, Discord

Started by an event in a connected app, and works across RSS. 9 steps: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 2Service 6

The steps in the order they run, from what starts it.

  1. 1When Newsletter Issue PublishedRss Feed Read triggerStarts it
  2. 2Create AI PromptCodeLogic
  3. 3Generate Announcements with OpenAIHttp RequestService
  4. 4Extract AI Generated CopyCodeLogic
  5. 5Authenticate Bluesky SessionHttp RequestService
  6. 6Publish on TelegramHttp RequestService
  7. 7Publish on DiscordHttp RequestService
  8. 8Forward Drafts to Slack ChannelHttp RequestService
  9. 9Publish to BlueskyHttp RequestService

How it's built

Starts on
An event in a connected app
Steps
9
Size
Medium: a working afternoon
Connects to
RSS
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own RSS account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.