FastHook Destinations

A Destination is a transport-level outbound target for a direct Connection. Provider operations belong in Workflow Actions.

Use a Connection when an accepted webhook should go directly to one receiver. Use a Workflow Action when FastHook should call Slack, Discord, Telegram, Twilio, Gmail, Google Sheets, or another connected application.

Supported Destination Types

FastHook exposes six destination types for new configurations. See Destination types for their field-by-field reference.

  • HTTP: deliver events to an HTTPS receiver.
  • CLI: forward events through fasthook-cli to a local service.
  • POSTGRESQL: insert events into an existing PostgreSQL table.
  • SENDGRID_EMAIL: send email through SendGrid Mail Send.
  • CLOUDFLARE_R2: archive event objects in Cloudflare R2.
  • AWS_S3: archive event objects in Amazon S3.

n8n webhook nodes use an HTTP Destination with their production webhook URL. Mock responses are configured on Sources and inspected through the request bin. App-specific sends and mutations use Actions with connected accounts.

What a Destination Owns

  • Target: receiver URL, CLI path, database table, email recipient, or object key.
  • Method: the outbound HTTP method for HTTP delivery.
  • Authentication: receiver credentials, signatures, or storage/database credentials.
  • Rate limit: pacing at the destination boundary.
  • State: enabled or disabled.
  • Evidence: response status, response body, latency, and delivery attempts.

When several Connections target the same receiver, reuse one Destination. This keeps credentials, delivery capacity, and attempt history attached to one operational object.

HTTP Destinations

Use HTTP for deployed services, webhook consumers, internal gateways, staging endpoints, and automation webhook URLs such as n8n.

Configure the endpoint URL, method, optional rate limit, and one of the supported authentication modes. FastHook signature auth lets your receiver verify outbound delivery. Custom headers and OAuth2 modes are available when the receiver requires them.

See Destination delivery signatures and Control throughput.

CLI Destinations

A CLI Destination forwards deliveries through an authenticated local tunnel:

Shell
fasthook login --api-key fhp_xxx
fasthook tunnel --destination des_xxx --to 8080

The Destination stores the path, method, status, and rate limit. The active CLI process supplies the localhost host and port through --to. FastHook stores the local response as delivery evidence.

See CLI & Tunneling.

PostgreSQL Destinations

PostgreSQL Destinations insert one row per delivered event into an existing table. Configure a least-privilege account, TLS, schema and table names, a JSONB payload column, and optional event ID, metadata, and delivery-time columns.

Delivery is at least once. Use a unique event ID column with ON CONFLICT DO NOTHING when duplicates are not acceptable. FastHook does not create or migrate the destination table.

See the PostgreSQL reference.

SendGrid Email Destinations

SendGrid Destinations send routed events through Mail Send. Configure a verified sender, recipient templates, subject and body templates, and an API key with the smallest required permission set.

Use filters before the Destination so only email-worthy events create messages. SendGrid remains a transport Destination until an equivalent connected-account Action is available.

See the SendGrid Email reference.

Cloudflare R2 Destinations

R2 Destinations write one object per delivery through the Cloudflare S3-compatible API. Configure account ID, bucket, object-key template, and scoped credentials. Prefer write-only credentials restricted to the destination bucket.

See the Cloudflare R2 reference.

AWS S3 Destinations

S3 Destinations write one object per delivery using AWS Signature Version 4. Configure region, bucket, optional endpoint, object-key template, and a least-privilege access key.

See the AWS S3 reference.

Provider Operations Are Actions

Use Workflow Actions for:

  • Google Sheets row and range operations.
  • Gmail messages and drafts.
  • Slack and Discord messages.
  • Telegram bot messages.
  • Twilio SMS, MMS, WhatsApp, and voice operations.

Actions reuse connected accounts, expose provider-specific schemas, and participate in ordered Workflow execution. Browse the integration catalog to see each provider's supported operations.

Delivery Practices

  • Use separate Destinations for production, staging, and local development.
  • Configure receiver authentication before enabling production traffic.
  • Match rate limits to receiver capacity.
  • Make receivers idempotent because delivery and replay are at least once.
  • Inspect attempts before retrying a broad event window.
  • Disable a Destination before rotating credentials or performing receiver maintenance.

Related Docs