PostgreSQL is the open-source relational database that powers production applications, analytics warehouses, and internal tools. The NoClick PostgreSQL node connects to any reachable database with a connection string or individual host credentials, then runs parameterized SELECT queries, executes INSERT/UPDATE/DELETE statements, and manages tables, schemas, indexes, views, sequences, and extensions. Because it speaks raw SQL, you can wire live database data into automations without writing a separate backend service. Every read and write step in a workflow can pull from or commit to the same database your app already uses.
Add a credential to the PostgreSQL node using either a full connection string in the form postgresql://user:password@host:port/database, or individual fields for host, port, database, username, and password. You can also set the SSL mode, which is required by most managed Postgres providers. The database must be reachable from NoClick's servers.
Yes. Both the SELECT query and the execute statement operations accept a separate parameters array, and you reference those values in your SQL as $1, $2, and so on. NoClick binds the parameters server-side, so values coming from upstream nodes are never concatenated into the query string. This is the recommended way to pass dynamic data from a form, webhook, or earlier node.
Run Select Query is for SELECT statements and returns rows as JSON, with a configurable row limit up to 10,000. Execute SQL Statement is for INSERT, UPDATE, DELETE, and other non-SELECT statements; it reports the affected row count and can optionally return rows when your statement includes a RETURNING clause. For very large result sets, the cursor-based query operation streams results in batches.
Yes. Beyond querying, the node can create and drop tables, schemas, indexes, and views, truncate tables, install extensions, and inspect structure with list-tables, list-columns, and get-table-info operations. It can also run maintenance operations like VACUUM and ANALYZE. This lets a workflow provision or clean up database objects as part of an automation.
It does. The node exposes Begin Transaction, Commit Transaction, and Rollback Transaction operations so you can group several statements into one atomic unit. If a step inside the transaction fails, you can route the workflow to a rollback so no partial change is left behind.