← Back to list
01Issue
BugShippedSwamp ClubPublic
AssigneesNone
Relationships
↔ sibling #4556#4533 Docs: webhook payload is only in scope in trigger.inputs; document run id header and route reload
Opened by stack72 · 11/8/2026· Shipped 11/10/2026
What is wrong
The manual contradicts itself on where webhook payload data is available, and it misses changes from swamp-club#3434.
- The workflows reference says no inputs come from the payload.
content/manual/reference/workflows.md, around lines 158-160 and 557, says a webhook run "extracts no inputs from its payload (the body is used only for signature verification)".- In fact
trigger.inputsis evaluated against the payload, so${{ webhook.body.* }},webhook.headersandwebhook.routemap payload fields to workflow inputs. Code:src/serve/deps.ts, theTriggerInputResolvercall.
- The how-to and the webhooks reference say
webhook.*works anywhere in the workflow.content/manual/how-to/set-up-webhooks.md, step 3 of the Telegram section, uses${{ webhook.body.message.chat.id }}directly in step inputs.content/manual/reference/swamp-serve/webhooks.md, "CEL context", says the namespace "is available in CEL expressions within that workflow".- In fact
webhook.*is in scope only insidetrigger.inputs. In step inputs or aguardit fails withUnknown variable: webhook. The working pattern is to map the field intrigger.inputsand readinputs.<name>in the step.
- New in swamp-club#3434, not yet documented:
- Every queued webhook response carries the run id in an
X-Swamp-Run-Idheader. That includes extensionrespondreplies that also enqueue. The JSON body is unchanged. - A replayed delivery keeps the same run id. A refused run has no record, and its
webhook_deniedevent and audit entry name the id. swamp serve reloadcan add the first webhook route to a serve that started with none.- Routes from
--webhookflags are fixed until restart. Reload warns when the config file also lists webhooks. - The dashboard Webhooks page and the admin health snapshot show each route's source (
configorflag).
- Every queued webhook response carries the run id in an
Suggested changes
- In the workflows reference, replace the "no inputs are extracted" wording with a
trigger.inputsexample that mapswebhook.bodyfields, and say this is the only place the namespace exists. - Rewrite the Telegram step 3 to map
chatIdandtextintrigger.inputsand readinputs.chatIdandinputs.textin the step. - In the webhooks reference, scope the "CEL context" section to
trigger.inputs. Add theX-Swamp-Run-Idheader to the response table, and a short note on reloading routes (file list reloads, flags do not).
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Editable. Press Enter to edit.
system commented 11/8/2026, 11:54:59 PM
Classified automatically when this issue was filed.
- Type: Bug
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.