Retweet cleanup with scheduling for X/Twitter
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs on a schedule (every day at 09:00) (plus 1 other trigger). Along the way it connects X (Formerly Twitter) and Slack.
How it runs
Trigger: On a schedule (every day at 09:00) (plus 1 other trigger).
- CONFIG | User Variables (Set Fields) (Edit Fields (Set)): sets or maps fields
- DLQ | Format error (Set) (Edit Fields (Set)): sets or maps fields
- FETCH | Get user ID by username (X API) (HTTP Request): calls an HTTP API
- FETCH | Latest tweets (X API) (HTTP Request): calls an HTTP API
- SPLIT | One item per tweet (Split Out): splits a list into separate items
- If: checks a condition and branches into true / false
- LOOP | Split in batches (rate-limit friendly) (Loop Over Items (Split in Batches)): loops over the items in batches
- SEND | Unretweet (delete retweet) (X (Formerly Twitter)): delete
- Wait: pauses before continuing
- NOTIFY | Slack (optional) (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - If
n8n-nodes-base.if - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - X (Formerly Twitter)
n8n-nodes-base.twitter - Wait
n8n-nodes-base.wait - Slack
n8n-nodes-base.slack - Error Trigger
n8n-nodes-base.errorTrigger
From the author
Who’s it for Social media managers, creators, and brand accounts that rely on retweets for reach but want an automated, hands-off cleanup after campaigns to keep profiles tidy and on-brand. What it does / How it works On a schedule, the workflow resolves your…