Repository navigation
Say the node installs on n8n Cloud and self-hosted n8n, and stop counting 151 platforms - #39
Merged
Merged
Conversation
The README, Getting started and Limitations all said the package runs on self-hosted n8n only, because n8n Cloud installs only verified community nodes and the submission was pending. It is now a verified community node, listed at n8n.io/integrations/hookdeck-event-gateway, so someone on n8n Cloud reading the Quickstart was told they could not use it. The install steps now start from the nodes panel, which is the route on both, and keep the package-name route for self-hosted instances with verified nodes turned off. The README also said "signature verification for 151 providers" and "Twilio and 147 more". v0.4.0 lists 817 source types, and the npm page shows this README, so the release was described with its previous count. The opening now says "more than 800 platforms": 814 named platforms less the 13 that take no secret leaves 801. The table says "hundreds more" rather than a number, which is what went stale last time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first commit described the package-name install only as the route for self-hosted instances with verified nodes turned off, which reads as a fallback. Self-hosted n8n is where much of this package's use is, and it is fully supported: from the nodes panel, as on n8n Cloud, or by package name from Settings → Community Nodes. The Quickstart and Getting started now list n8n Cloud first, then self-hosted n8n as a path of its own. Both say a self-hosted instance doesn't need a public address, because the trigger delivers through the Hookdeck CLI when Hookdeck can't reach it, and point at Transport for the detail. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leggetter
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README, Getting started and Limitations still said the package runs on self-hosted n8n only, pending n8n's verification. It is a verified community node now (https://n8n.io/integrations/hookdeck-event-gateway/), so the Quickstart was telling n8n Cloud users they couldn't use it.
Docs only, no code changes. The npm page shows this README, so it currently describes v0.4.0 with the 0.3.0 count.
🤖 Generated with Claude Code