OpenRuna
Sign in
← Workflows

ETL pipeline

9 nodes · twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron

Engine
n8n
Nodes
9
Trigger
scheduled/triggered
Source file
1108_Postgres_Googlecloudnaturallanguage_Automation_Scheduled.json

Workflow flow

IntegrationsXPostgreSQLMongoDBSlackGoogleCloudNaturalLanguageCronIFNoOpSet
100%

Cron

Cron

Twitter

X

MongoDB

MongoDB

Google Cloud Natural Language

GoogleCloudNaturalLanguage

Set

Set

Postgres

PostgreSQL

IF

IF

Slack

Slack

NoOp

NoOp

9 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

ETL pipeline (9-node n8n automation, twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "ETL pipeline" chains 9 nodes to move data between twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron. 9 nodes · twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron It starts from a scheduled/triggered trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 9-node flow from scratch.
  • Benchmark it against your current twitter integration to spot missing steps or redundant nodes.
  • Study how data moves from twitter to postgres before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the twitter stack.

Example output

Imported into n8n, "ETL pipeline" exposes 9 configured nodes. Trigger type: scheduled/triggered. Integrations: twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron. Open each node after import to map credentials to your own twitter and postgres accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "ETL pipeline" JSON into a plain-English runbook, node by node. It can flag where twitter rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "ETL pipeline" — extract twitter IDs and secrets into environment variables without changing the 9-node structure.

Frequently asked questions

How do I import "ETL pipeline" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "ETL pipeline" use?
It uses: twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron. The flow diagram above shows how each service connects across the 9 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own twitter and postgres credentials in n8n after import.
What trigger type does "ETL pipeline" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "ETL pipeline" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for twitter, postgres, mongoDb, slack, googleCloudNaturalLanguage, cron.

Related resources