Skip to main content
A destination sends every matching event somewhere, retried until it arrives. Each destination has a type, chosen when you create it: All three use the same delivery machinery: the retry schedule, the send rate and concurrency limits, the monthly delivery allowance and its holds, replay, the delivery log, and the failure streak that switches a failing destination off. Only the request differs. See Destinations and deliveries. By default a webhook’s body is Hookie’s envelope, {id, dataset, received_at, data}. A webhook can also carry its own headers, a credential and a body template, so you can send straight to services such as Datadog or an email API without a relay in between. Choose the type under Type when you choose Add destination on a project’s Connections tab. A destination’s type is fixed once it exists: to change it, create a new destination of the type you want. Set the rest on the destination’s tile under Request options, or when you create it. From preset fills them in for Slack, Datadog and email.

Slack

A Slack destination posts each event to a channel through a Slack incoming webhook. If the Connections tab shows Add to Slack, choose it and pick a channel on Slack’s screen: Hookie creates the destination for you, with no URL to copy. See Add to Slack. Otherwise:
  1. Install the Hookie Slack app to the channel, and copy its Incoming Webhooks URL. It starts https://hooks.slack.com/services/. Anyone who holds the URL can post to the channel, so treat it like a password. Any Slack app with an incoming webhook works too.
  2. In the console, open the project’s Connections tab. Choose Add destination, then Slack under Type. Or choose From preset, then Slack (Incoming Webhook).
  3. Paste the URL into Slack incoming-webhook URL, and give the destination a name.
  4. Optional: set a Dataset filter, so only the datasets you want in the channel are sent.
  5. Choose Create.
Only a https://hooks.slack.com/ URL is accepted (/services/…, /workflows/… or /triggers/…). Hookie stores it encrypted and only ever shows a masked hint, such as https://hooks.slack.com/services/••••abcd, on the tile, in the API and in the delivery log. It is never exported. To replace it, choose Edit… on the tile and paste the new URL; leave the field blank to keep the saved one.

The message

Each event becomes an alert card:
  • a title from the payload, such as its title or summary, or New event in and the dataset;
  • a severity badge and a coloured bar, when the payload’s severity, level, priority, status or state says how bad it is;
  • up to 10 of the payload’s fields;
  • the payload as pretty-printed JSON, only when the fields left something out. A payload over 2,500 characters is cut there, with a note of its full length, so Slack never refuses a large record;
  • a View in Hookie button that opens the dataset’s records;
  • the dataset, the event id and when the event arrived.
The notification text is the severity, the title and the dataset. See What a card shows for the details. To write your own message instead, choose JSON template under Body. A template replaces the default message, so it must be a Slack message body:
Placeholders work as they do for any body template.

What Slack is sent

A POST with Content-Type: application/json and User-Agent: Hookie/1.0. There are no signature headers, because Slack checks none: the URL is the credential. A Slack destination takes no custom headers and no authentication.

Slack’s answers

Unlike a webhook, a Slack destination does not retry a 404. After 10 dead deliveries in a row, over at least an hour, Hookie switches the destination off, as for any destination. Fix the URL with Edit…, then choose Re-enable to send what it held.
A Slack URL is refused as an HTTPS webhook’s URL, with 400, and as a customer portal destination’s URL. That keeps every Slack URL encrypted: create a Slack destination instead.

S3-compatible storage

An S3 destination writes each event as one JSON object in a bucket. It works with AWS S3, Cloudflare R2, Google Cloud Storage in interoperability mode, and MinIO. Each request is signed with AWS Signature Version 4. The endpoint is the service’s origin only, with no path: the bucket goes in Bucket. It must be a public https address. For Google Cloud Storage, the endpoint is https://storage.googleapis.com, the region auto, and the keys an HMAC key from the bucket’s Interoperability settings.

Set up AWS S3

  1. Create the bucket, or choose an existing one, and note its region.
  2. In IAM, create a user for Hookie and attach a policy that allows s3:PutObject on the bucket and prefix, and nothing more:
    Hookie only writes. It never reads, lists or deletes objects. If the bucket encrypts with a customer-managed KMS key, the user also needs kms:GenerateDataKey on that key.
  3. Create an access key for the user.
  4. In the console, open the project’s Connections tab. Choose Add destination, then S3-compatible bucket under Type.
  5. Leave Endpoint empty. Enter the Region, the Bucket, an optional Key prefix, the Access key id and the Secret access key, then choose Create.

Set up Cloudflare R2

  1. In the Cloudflare dashboard, create the R2 bucket, or choose an existing one.
  2. Under R2 → Manage API tokens, create an API token with Object Read & Write permission, applied to that bucket only. R2 has no write-only permission, and Hookie only writes. Copy the token’s Access Key ID and Secret Access Key.
  3. Note your account’s S3 API endpoint, https://<account id>.r2.cloudflarestorage.com. The bucket’s settings show it with the bucket name on the end: leave that part off.
  4. In the console, choose Add destination, then S3-compatible bucket. Enter the Endpoint, leave Region empty for auto, and enter the Bucket, an optional Key prefix and the two keys. Choose Create.

Where each object goes

Each event is written to:
The date is when Hookie received the event, in UTC. With the prefix hookie/, an orders event received on 1 October 2026 is written to hookie/orders/2026/10/01/rec_….json. The prefix is put in front exactly as you write it, so end it with / to make it a folder: hookie would give hookieorders/…. It may be up to 256 characters, and may not start with / or contain . or .. segments, backslashes or control characters. The object is the body Hookie would send: the envelope by default, or your template or field mappings. It is stored as application/json, with the metadata x-amz-meta-hookie-event-id and x-amz-meta-hookie-dataset. There are no Hookie signature headers; the request is signed with your key instead. Hookie addresses AWS buckets as https://<bucket>.s3.<region>.amazonaws.com/<key>, and uses path-style addresses (<endpoint>/<bucket>/<key>) for a custom endpoint and for a bucket name with a dot in it.

Retries and replays overwrite

The object key comes from the event, never from the attempt: its prefix, dataset, received date and id. So a retry, a replay, or an event Hookie hands on twice writes the same object again, rather than a second copy. Each event leaves one object per destination. If the bucket has versioning on, a rewrite adds a version. Unlike a webhook, an S3 destination does not retry a 404. The secret access key is stored encrypted, never returned, exported or logged, and is removed from any error text before it reaches the delivery log. The access key id is not secret and is shown. To rotate the key, choose Edit… and enter the new access key id and secret access key; leave the secret blank to keep the saved one. An S3 destination takes no custom headers and no authentication.

Signing secret on Slack and S3 destinations

Every destination has a signing secret (whsec_…). Slack and S3 deliveries are not signed with it, so the console labels it Signing secret (alert notices only): it signs the notices sent to the destination’s alert URL. Owners and admins can still reveal and rotate it on the tile.

Custom headers

HTTPS webhook destinations only. Add up to 20 headers. Mark a header Secret when its value is a credential: it is stored encrypted and is never shown again, in the console, the API or the audit log. To keep a saved secret header while you edit others, leave its value blank. Hookie sets some headers itself, and you cannot override them:
  • Hookie-*, X-Hookie-* and webhook-*
  • Content-Type, Content-Length, Host, User-Agent and Idempotency-Key
  • hop-by-hop headers such as Connection, Transfer-Encoding and Upgrade

Authentication

HTTPS webhook destinations only. Choose one: The credential is stored encrypted and is never returned. The destination shows only the type, and for an API key, the header name. To change the header without re-entering the key, leave the key blank.

Body

Every type takes a body. For a Slack destination, the default is the Slack message rather than the envelope. A placeholder is a dotted path into the envelope: {{dataset}}, {{id}}, {{received_at}}, {{data.customer.email}}. {{data}} alone is the whole payload.
A string that is exactly one placeholder keeps the value’s type, so "{{data.total}}" sends a number. A placeholder inside a longer string becomes text, and a missing value becomes an empty string. Templates are data, never code. A placeholder is a path lookup, and nothing is evaluated.
The body is always JSON. For an HTTPS webhook, Hookie-Signature is computed over the body exactly as sent. Verify a templated body the same way as the envelope (see Verify signatures).

When a destination keeps failing

A delivery goes dead when its retries run out, or at once when your receiver refuses it with a 4xx that is never retried, such as 400, 401 or 403. Retrying deliveries do not count.
  1. At the first dead delivery, the destination is flagged as failing, with the last error, on its tile and on Home.
  2. After 10 dead deliveries in a row over at least an hour, Hookie switches the destination off. The reason is shown on its tile and on Home, and the audit log records destination_auto_disabled.
  3. While it is off, new deliveries are held, not lost. Click Re-enable on Home or on the tile to send them and start the count again.
A single delivery that arrives ends a failing streak at any point.

Alert webhook

Set an Alert URL on the destination to be told when Hookie switches it off. Hookie POSTs one notice to it:
For a Slack destination, destination.url is the masked hint; for an S3 destination, it is the bucket’s address. The notice carries Hookie-Signature, signed with the destination’s own signing secret, and Hookie-Alert: destination.disabled. It is sent once and is not retried. The alert URL must be a public https address. Hookie does not send email alerts.

When your plan changes

Each plan caps how many destinations and database sources a workspace runs, across all its projects, and how often a source may poll: When the workspace moves to a plan with lower caps (a downgrade, a cancellation, or a trial ending), Hookie brings what is running in line with the new plan straight away:
  • Destinations and sources over the cap are paused, newest first. The oldest keep running. A paused one shows a Paused: over plan limit tag, with a link to billing. A paused destination’s deliveries wait as paused, like any disabled destination’s, rather than being lost.
  • Poll intervals below the new minimum are raised to it. They are not lowered again if you upgrade later; set them yourself.
  • One plan_limits_applied entry in Settings → Audit log lists everything that was paused, resumed or slowed.
When the plan rises again, only what Hookie paused is resumed, oldest first, as far as the new caps allow. A resumed destination sends its waiting deliveries, and a resumed source starts polling again. What you switched off stays off. Hookie never turns on a destination or source you disabled yourself, on any plan change. Switching one on or off yourself also takes it out of Hookie’s hands, so it is not resumed automatically later. Turning one on while the workspace already runs its cap is refused with 402: disable another first, or upgrade. A destination that belongs to a customer portal customer is paused the same way. The customer cannot turn it back on from the portal while it is over the limit, and is told to contact you. Over the API, destinations and sources carry paused_reason: "over_plan_limit" when Hookie paused them for the plan, null otherwise.

API

POST and PATCH /admin/api/projects/{project_id}/destinations take headers, auth, transform and alert_url. PATCH with {"enabled": true} re-enables a destination and clears its failing state. The dataset filter is datasetFilter on POST and dataset_filter on PATCH: a list of dataset names, or null for every dataset. An empty list is refused with 400, because it used to mean every dataset rather than none. POST also takes type: webhook (the default), slack or s3. A Slack or S3 destination is addressed by config instead of url:
For S3, endpoint is left out (or null) for AWS, and region is required then. config.secret_access_key and config.webhook_url are write-only.
  • A Slack or S3 destination refuses url, headers and auth with 400. A webhook refuses config, and refuses a hooks.slack.com URL.
  • A destination comes back with type, config and secrets_set. config never holds a credential: a Slack destination’s webhook_url is the masked hint, and an S3 destination’s has endpoint, region, bucket, prefix and access_key_id. secrets_set names the credential held, ["webhook_url"] or ["secret_access_key"]. A webhook has config: null. Its url is a display value: the masked Slack URL, or the bucket’s address.
  • PATCH with config changes a Slack or S3 destination’s settings. Settings you leave out keep their stored values, and so does a credential you leave out. PATCH with a different type is refused with 400.
Edit or delete. A destination’s Edit… changes its name, URL and dataset filter, or a Slack or S3 destination’s settings and credential; over the API, PATCH takes name, and url or config, too. It stays the same destination, with the same id and signing secret, so your receiver keeps verifying. A new URL must be https, and a destination that belongs to a customer portal customer keeps its URL (409): it is theirs to change. Delete removes a destination that has never had a delivery outright. One with delivery history leaves the project for good, and its past deliveries keep its name, so the delivery log still says where each one went. GET /admin/api/dashboard/summary lists failing destinations in failing_destinations. See the API reference.