Skip to content

Document webhook custom URLs - #849

Open
elias-ba wants to merge 1 commit into
mainfrom
webhook-custom-urls
Open

Document webhook custom URLs#849
elias-ba wants to merge 1 commit into
mainfrom
webhook-custom-urls

Conversation

@elias-ba

@elias-ba elias-ba commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

⚠️ Ready for review, but don't merge yet. This goes out with the Lightning release that carries custom URLs. A merge to main deploys to docs.openfn.org on its own, with no manual step, so it can't land ahead of the release.

Short Description

Documents webhook custom URLs on the Triggers page. A webhook trigger can be given a name, so it answers on /i/<project-id>/<name> as well as on its generated /i/<trigger-id> URL.

Details

The page never said what a webhook's URL looks like or where to find it, so this is the first time it explains them at all. The new section covers both URL shapes, what a name may contain, that names are unique within a project, and that renaming or removing one breaks it with no redirect.

The rules are taken from the implementation rather than from the feature description. Shipped in OpenFn/lightning#5105 and OpenFn/lightning#5111, with the CLI half in OpenFn/kit#1511.

The Kafka trigger docs on this same page are stale for a different reason, and #850 handles that separately.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our Responsible AI Policy

The Webhook Event Triggers section never said what a webhook's URL looks like or
where to find it, so there was nothing to extend: a reader had no way to learn
that a trigger can now answer on a name you choose as well as on its id.

Covers both URL shapes, what a name may contain, that names are unique per
project, and that renaming or removing one breaks it with no redirect. That last
one is the trap worth the warning, since the sending system has to be updated
first.
@elias-ba elias-ba mentioned this pull request Sep 4, 2026
3 tasks
@elias-ba
elias-ba marked this pull request as draft September 4, 2026 22:59
@elias-ba
elias-ba marked this pull request as ready for review September 5, 2026 02:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant