PostgreSQL Tools

The PostgreSQL provider connects directly to a PostgreSQL database to run raw SQL queries and perform structured insert, update, and delete operations. Use it in a workflow whenever you need to read from or write to a Postgres database — for example pulling rows to feed an agent, persisting results, or maintaining application data.

Overview

This tool does not use an HTTP API key or OAuth. It authenticates by opening a pooled connection to your PostgreSQL server using the host, database, username, and (optional) password you supply. Enable ssl for encrypted connections to managed/cloud databases.

Operations

There is a single tool that handles all four operations. Pick the operation with the action parameter: execute, insert, update, or delete.

Configuration

postgresql_database

Notes from the implementation:

• execute runs your raw query (optionally parameterized) and returns the result rows.
• insert builds an INSERT statement from the data object/array; table and column identifiers are sanitized.
• update builds UPDATE ... SET ... WHERE ... from data (SET clause) and conditions (WHERE clause).
• delete builds DELETE FROM ... WHERE ... from conditions.

Outputs

postgresql_database

• success (boolean) — Whether the operation was successful.
• data (array, optional) — Query result rows for SELECT/execute operations (also used to carry structured error records).
• affectedRows (number, optional) — Number of rows affected by INSERT/UPDATE/DELETE.
• error (string, optional) — Error message if the operation failed.
• metadata (object, optional) — Execution metadata: executionTime (ms), rowCount, and columns (column names for query results).

The block also surfaces an errorDetails (json) output with detailed error information including type and execution time.

YAML Example

postgresql_1:
  type: postgresql
  name: "PostgreSQL"
  inputs:
    action: "execute"
    host: "db.example.com"
    port: 5432
    database: "my_database"
    username: "postgres"
    password: "{{POSTGRESQL_PASSWORD}}"
    ssl: true
    query: "SELECT id, email FROM users WHERE active = true"
  connections:
    outgoing:
      - target: next-block-id

Insert example (set action: "insert"):

postgresql_2:
  type: postgresql
  name: "PostgreSQL"
  inputs:
    action: "insert"
    host: "db.example.com"
    database: "my_database"
    username: "postgres"
    password: "{{POSTGRESQL_PASSWORD}}"
    table: "users"
    data: '{"name": "John Doe", "email": "john@example.com", "active": true}'
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth is via database credentials, not an API key. Store the password in an environment variable and reference it as {{POSTGRESQL_PASSWORD}} rather than hardcoding it.
• Set ssl: true for managed/cloud Postgres (Supabase, RDS, Neon, etc.); most require TLS. The pool connects with rejectUnauthorized: false, so it accepts self-signed certs.
• Match the action to its required fields: execute needs query; insert/update need table + data; update/delete need conditions. Conditions are combined with AND on exact equality only.
• Reference upstream block outputs inside your query or data with double-brace syntax, e.g. {{agent2.content}} or {{variable.userId}}. Prefer parameterized queries ($1, $2) for user-supplied values to avoid SQL injection.