ETL pipeline for text processing
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on a schedule (legacy Cron node). Along the way it connects X (Formerly Twitter), Postgres, MongoDB and Slack and 1 more.
How it runs
Trigger: On a schedule (legacy Cron node).
- Twitter (X (Formerly Twitter)): search
- MongoDB: insert
- Google Cloud Natural Language: uses Google Cloud Natural Language
- Set (Edit Fields (Set)): sets or maps fields
- Postgres: uses Postgres
- If: checks a condition and branches into true / false
- Slack: uses Slack
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron: replace with Schedule Trigger.
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
Nodes used (9)
- X (Formerly Twitter)
n8n-nodes-base.twitter - Postgres
n8n-nodes-base.postgres - MongoDB
n8n-nodes-base.mongoDb - Slack
n8n-nodes-base.slack - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Google Cloud Natural Language
n8n-nodes-base.googleCloudNaturalLanguage - Edit Fields (Set)
n8n-nodes-base.set - Cron
n8n-nodes-base.cron
From the author
This workflow allows you to collect tweets, store them in MongoDB, analyse their sentiment, insert them into a Postgres database, and post positive tweets in a Slack channel. Cron node: Schedule the workflow to run every day Twitter node: Collect tweets…