v0.3.0

The action node can now set up a source the same way the trigger does, and the trigger tells you when it is about to ignore what you typed. Nothing you have built changes, and no workflow needs republishing.

Added

Source → Get or Create asks the same questions the trigger does. Source Type, Verification, and labelled fields for HMAC, API key, basic auth and platform secrets. Creating a verified Stripe source used to mean hand-writing {"auth_type":"STRIPE","auth":{"webhook_secret_key":"..."}} into Source Config (JSON) while the trigger two nodes away had a field for it. The JSON field is still there for schemes the fields cannot express, and still wins where they overlap.

Fixed

The trigger says when it will not apply your source settings. Picking an existing source from the list adopts it exactly as Hookdeck has it configured — Source Type, Verification and the secret fields are ignored unless Options → Update Existing Source is on. The only sign of that used to be a warning logged after publishing, by which point you had filled the fields in and believed verification was configured. A notice now appears while you are configuring, as soon as you pick a source.

The fields stay editable rather than being greyed out or hidden: n8n resets a greyed-out field to its default, and drops a hidden one when the workflow saves, so either would have taken a webhook secret you had just typed.

Changed

The README is now about what the package is and how to start. The reference material it used to carry — every trigger option, the CLI route, signature verification, the action node's operations and the reliability contract — moved into docs/. The documentation links on both nodes and on the credential point at those pages.

Full Changelog: v0.2.1...v0.3.0

v0.2.1

A maintenance release. Nothing you have built changes, and no workflow needs republishing.

Fixed

Delivery group errors say what went wrong. Configuring Delivery Group Key on a project without the feature used to fail on publish with {"level":"info","handled":true,...} in front of the actual reason, which reads like a broken node rather than a feature you have to ask for. It now says Delivery groups are not enabled for this organization. The field's description now tells you delivery groups are an early access feature before you hit that, rather than after.

Changed

Both nodes are easier to find in the nodes panel. They are filed under Communication as well as Development, and they now carry search aliases — searching webhook, event, ingest, reverse proxy, queue, retry or replay finds them, and the trigger also answers to tunnel and localhost.

Housekeeping

version in package.json tracks what is on npm again. It read 0.1.0 while npm served 0.2.0, because the publish workflow took the version from the release tag rather than from the repository — so no commit recorded the version anyone was installing. Releases now bump package.json before the release exists, and the workflow refuses a tag that disagrees with it.

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Summary

The Hookdeck Event Gateway Trigger no longer appears in an AI Agent's tool list. It was
never usable there — a trigger waits for Hookdeck to deliver an event, so an agent that
picked it got a tool it could not call. The Hookdeck Event Gateway action node is still
available as a tool, and is the one you want an agent using.

This is the only change to the nodes themselves since v0.1.0. Everything else in the range
is tests, CI and documentation.

Upgrading is enough — there is nothing to reconfigure and no need to republish a workflow.

Fixes

• An AI Agent's tool list no longer offers Hookdeck Event Gateway Trigger Tool. n8n
  generated that entry automatically because the trigger declared itself usable as a tool;
  an agent that selected it wasted a turn on something that cannot be invoked. Removing it
  also brings the package in line with n8n's current community-node rules, which now treat a
  trigger opting into the tool picker as an error.

Internal

• @n8n/scan-community-package 0.31.0 → 0.32.0, @n8n/node-cli 0.42.2 → 0.44.5.
  The newer scanner is what flags a trigger opting into the tool picker; a caret range on a
  0.x version could not reach the new minor, so the check kept passing against the old rule.
• Live test suites consolidated under test/live and hardened against the Hookdeck API rate
  limit.

---

Full Changelog: v0.1.0...v0.2.0

v0.1.0

First release of the Hookdeck Event Gateway nodes for n8n.

Point a provider's webhooks at Hookdeck instead of directly at n8n, and Hookdeck handles the parts a workflow trigger cannot: signature verification, retries with backoff, deduplication, rate limiting, and a durable record of every event so nothing is lost when a workflow is down or fails.

Installation

Follow n8n's community nodes installation guide with the package name @hookdeck/n8n-nodes-hookdeck. A free Hookdeck account is enough to run real workflows.

Hookdeck Event Gateway Trigger

Publishing a workflow provisions a Hookdeck connection pointing at it, and deactivating tears it down — there is no separate setup in the Hookdeck dashboard to keep in step.

• 151 source types. Pick your provider and Hookdeck verifies its signatures at the edge; a forged request never reaches your workflow. Generic sources support HMAC, API key and basic auth, with a JSON escape hatch for schemes the fields cannot express.
• Works with a local n8n, with no tunnel. If your instance is not reachable from the internet, the trigger provisions a CLI destination instead of failing, and tells you the hookdeck listen command to run. Deliveries are signed identically either way, so what the workflow receives does not change between local and cloud.
• Retries and deduplication are on by default, whether or not you open Options: five exponential retries a minute apart on 5xx and 429, and a 60 second deduplication window.
• Deactivating pauses rather than deletes. Events that arrive while a workflow is down are held and delivered on the next activation, so a deploy loses nothing.
• Delivery metadata on every item as hookdeck — event ID, attempt count, and isLastAttempt for routing a final failure to a dead-letter branch.
• Acknowledgement modes. Async Retry answers Hookdeck on receipt; Sync holds the response until the workflow finishes, so a failed run returns an error and Hookdeck's retry rules apply to the run itself.
• Self-healing. If the instance moves host or path, the next activation re-points the existing connection instead of leaving a duplicate behind.

Hookdeck Event Gateway node

Attempts, Connections, Destinations, Events, Issues, Requests and Sources, with cursor-following Return All.

• Source → Get or Create returns the source's public URL as workflow data. The URL cannot exist before the source does, so this is how to obtain it without leaving n8n. It gets before creating, so re-running never overwrites an existing source.
• Get Count on Attempt, Connection, Destination, Event, Issue and Source. Both nodes are usable as agent tools, and without it an agent asking "how many failed events?" received a single page and reported its length as the total. Events have no count endpoint, so they are counted by paging to a ceiling and returned as a stated floor rather than a page size presented as a fact.

Example workflows

Two importable workflows in examples/, both run against a real n8n:

• Process each event once — an idempotency gate keyed on hookdeck.idempotencyKey
• Catch events on the final attempt — a dead-letter branch routed on hookdeck.isLastAttempt

Notes

0.0.1 on npm is a deprecated placeholder, published by hand only to claim the package name so releases could be published from CI with provenance. 0.1.0 is the first real release, and the first published from GitHub Actions.

---

Full Changelog: https://github.com/hookdeck/n8n-nodes-hookdeck/commits/v0.1.0