PostgreSQL Destination Configuration

PostgreSQL dashboard fields

PostgreSQL API config

{
  "name": "postgres-event-store",
  "type": "POSTGRESQL",
  "config": {
    "host": "db.example.com",
    "port": 5432,
    "database": "events",
    "schema": "public",
    "table": "webhook_events",
    "ssl_mode": "verify-full",
    "payload_column": "payload",
    "event_id_column": "event_id",
    "metadata_column": "metadata",
    "delivered_at_column": "delivered_at",
    "on_conflict": "IGNORE",
    "connect_timeout_seconds": 10,
    "auth_type": "POSTGRES_PASSWORD",
    "auth": {
      "username": "fasthook_writer",
      "password": "replace-with-a-secret"
    },
    "rate_limit": 5,
    "rate_limit_period": "second"
  }
}

Create the table and writer role

Run this once as a database administrator, replace the example password, and store that writer password in the destination. FastHook never creates or migrates the target table.

CREATE TABLE public.webhook_events (
  event_id text PRIMARY KEY,
  payload jsonb NOT NULL,
  metadata jsonb,
  delivered_at timestamptz NOT NULL DEFAULT now()
);

CREATE ROLE fasthook_writer LOGIN PASSWORD 'replace-with-a-secret';
GRANT CONNECT ON DATABASE events TO fasthook_writer;
GRANT USAGE ON SCHEMA public TO fasthook_writer;
GRANT INSERT ON TABLE public.webhook_events TO fasthook_writer;

If you use a different event ID column, keep a UNIQUE or primary-key constraint on that column before setting on_conflict to IGNORE.

PostgreSQL authentication

• PostgreSQL username and password
• TLS certificate verification

PostgreSQL delivery method and limit

Rate limit: Defaults to 5 inserts/second. Configure a lower or higher destination rate for your database capacity.

PostgreSQL delivery behavior

• FastHook performs one parameterized INSERT per delivery. Payload and metadata values never become SQL syntax.
• The payload column must be JSONB. Non-JSON source bodies are stored as a JSON string, so every delivery still produces valid JSONB.
• FastHook opens a short-lived connection inside the send Worker and closes it after the insert. The PostgreSQL driver is loaded only for PostgreSQL deliveries.
• The target must be publicly reachable. Cloudflare Workers block localhost and private-network addresses for ordinary outbound TCP sockets.
• FastHook does not create tables, columns, indexes, or constraints. Apply the documented DDL before enabling the connection.
• Delivery is at least once. Use event_id_column, a UNIQUE constraint, and on_conflict=IGNORE when side effects must be idempotent.

PostgreSQL setup checklist

1. Create the destination table and a least-privilege writer role in PostgreSQL.
2. Allow inbound PostgreSQL traffic from public networks according to your database provider's networking controls. Workers outbound TCP does not use a fixed single IP.
3. Create a FastHook destination and choose POSTGRESQL.
4. Enter host, port, database, credentials, TLS mode, schema, table, and column names.
5. For idempotency, configure an event ID column with a UNIQUE constraint and choose Ignore by Event ID.
6. Connect a source, send a test event, and inspect the attempt before routing production traffic.

PostgreSQL troubleshooting

Related docs

• Mock API destination
• Google Sheet destination
• Destinations
• Connections
• Control throughput
• Cloudflare TCP sockets
• Postgres.js