PostgreSQL Destination

When to use this destination type

Choose POSTGRESQL when the receiver target is PostgreSQL table. Destinations are outbound delivery targets: they do not decide whether a source request should be accepted, and they do not own connection filters or transformations. They own where the final delivery goes and how FastHook should authenticate, pace, disable, and inspect that delivery.

A destination can be reused by multiple connections when several source branches should feed the same receiver. Reuse keeps receiver capacity, credentials, and attempt evidence attached to one destination id.

FastHook dashboard fields

In the dashboard, create a destination, set Destination Type to POSTGRESQL, then fill the fields below.

API config fields

The REST API stores destination-specific behavior under config. Use PATCH for focused edits and PUT only when your request contains the full config you want to keep.

{
  "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"
  }
}

curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "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.

Authentication

Destination authentication is outbound. It helps the receiver trust or accept FastHook delivery, and it is separate from source authentication that verifies the original webhook producer.

• PostgreSQL username and password
• TLS certificate verification

Delivery operation and rate limit

This destination performs one INSERT per delivery attempt. Rate limits apply at the destination boundary, so every connection that targets the same table destination shares that capacity.

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

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.

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.

Troubleshooting

Related docs

• Destinations
• Connections
• Control throughput
• Cloudflare TCP sockets
• Postgres.js
• API reference