Webhook intake maps any payload onto a workflow's inputs #2032
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#2032
Reference in new issue
Block a user
Today a person (or an agent) can point any sender at a generated webhook endpoint, define the event types it sends, and map the event's fields onto a workflow's inputs through bindings, mappings and playbooks, with CEL
whenconditions andargs. The single binary's triggers only match fields exactly and pass the whole event as the input, and #1978 deletes the old path, so the capability would be lost.Keep the capability and change who builds it. A trigger becomes source, event type, a CEL
when, an input mapping and a workflow:internal/domain/eventtypemove into the events module's unmatched groups.internal/domain/eda/exprmoves into triggers forwhenand for mapping event fields onto workflow inputs, replacing bindings, mappings and playbookargs.The old code moves rather than being rewritten (MIGRATION.md in archie-product, row 2).
Done when: a payload from a sender Archie has never seen arrives at a generated endpoint, Archie drafts a trigger whose
whenand input mapping feed a workflow's inputs, and once published the next payload starts a run with those inputs.Locked in by the maintainer: this capability is the reason Archie was rewritten in the first place, and it stays. The names change (binding, mapping and playbook become parts of a trigger); the behaviour doesn't.