Pipedream PostgreSQL → n8n

5 Pipedream PostgreSQL actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: postgresql.

Actions

Pipedream action	n8n	Fit	Notes
postgresql-execute-custom-query	Postgres database → executeQuery	Check output	n8n option queryBatching default 'single' is fine for one item.
postgresql-insert-row	Postgres database → insert	Check output	n8n validates columns against the live table schema (unknown columns error, like PD's SQL error); json/jsonb and array columns are converted by n8n (>=2.4).
postgresql-find-row	Postgres database → select	Direct	Both SELECT * ... WHERE col = $1 without ORDER BY, first row.
postgresql-upsert-row	Postgres database → upsert	Check output	Both INSERT ... ON CONFLICT (<col>) DO UPDATE SET <other cols> = EXCLUDED/values RETURNING *; conflictTarget must have a unique/PK constraint. n8n throws if the conflictTarget value is missing/falsy in rowValues (e.g. 0 or '') - PD would attempt the insert.
postgresql-update-row	Postgres database → update	Check output	Semantic differences: PD updates only ONE row (WHERE col = (SELECT col ... ORDER BY col LIMIT 1)), n8n updates ALL rows matching column=value; n8n throws 'The row you are trying to update doesn't exist' when nothing matches (PD returns undefined); if…

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
postgresql-new-row	Postgres Trigger	Check output	SEMANTICS CHANGE: PD polls (SELECT * WHERE <column> > last ORDER BY DESC; emits 10 initial rows on deploy; catches rows inserted while paused; read-only access suffices). postgresTrigger creates a plpgsql function + AFTER INSERT trigger on the table and…
postgresql-new-or-updated-row	Postgres Trigger	Check output	PD polls by timestampColumn (> last value) and dedupes by identifier+timestamp; n8n is push-based via DB triggers (same caveats as postgresql-new-row: CREATE TRIGGER privileges, persistent LISTEN connection, no catch-up while inactive). Every UPDATE fires,…

Credentials

Create a PostgreSQL credential in n8n (type postgres). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a PostgreSQL node?+

Yes. 5 of the 5 Pipedream PostgreSQL actions listed here map to a native n8n node.

Will my Pipedream PostgreSQL connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a PostgreSQL credential in n8n (type postgres) and select it on the converted nodes.

Are Pipedream PostgreSQL triggers supported in n8n?+

2 of the 2 Pipedream PostgreSQL event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the PostgreSQL API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana Calendly ClickUp Discord Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini All apps →