The flow
Starts it 2Logic 6Service 4
The steps in the order they run, from what starts it.
- 1TRIGGER | Schedule (09:00 server time)Schedule triggerStarts it
- 2ON ERROR | CaptureError triggerStarts it
- 3CONFIG | User Variables (Set Fields)SetLogic
- 4DLQ | Format error (Set)SetLogic
- 5FETCH | Get user ID by username (X API)Http RequestService
- 6FETCH | Latest tweets (X API)Http RequestService
- 7SPLIT | One item per tweetSplit OutLogic
- 8IF | Is retweet?IfLogic
- 9LOOP | Split in batches (rate-limit friendly)Split In BatchesLogic
- 10SEND | Unretweet (delete retweet)TwitterService
- 11WAIT | Delay between API callsWaitLogic
- 12NOTIFY | Slack (optional)SlackService
How it's built
- Starts on
- A clock
- Steps
- 12, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Slack, X
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack and X accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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. 12 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.
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 12 steps before you point it at anything that matters.