Join data from Postgres and MySQL
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects MySQL and Postgres.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- PegarConfiguracaoImpressao (HTTP Request): calls an HTTP API
- dadosProduto (MySQL): run a query
- trataRetorno (Function): runs custom JavaScript (legacy Function node)
- roloProduto (Merge): merges the data from its input branches
- dadosRolo (Postgres): run a query
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:
- Function (legacy) in trataRetorno: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) trataRetorno | Code node, mode 'Run Once for All Items' |
Nodes used (6)
- Webhook
n8n-nodes-base.webhook - MySQL
n8n-nodes-base.mySql - HTTP Request
n8n-nodes-base.httpRequest - Postgres
n8n-nodes-base.postgres - Function
n8n-nodes-base.function - Merge
n8n-nodes-base.merge
From the author
query data from two different databases handle and unify in a single return