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