Webhook intake maps any payload onto a workflow's inputs #2032

Open
opened 2026-11-16 10:11:02 +00:00 by sam · 1 comment
Owner

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 when conditions and args. 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:

  • Any sender gets a generated endpoint with its own token or signing scheme (#2021), and a generic webhook connector stores any JSON body as the event, with no vendor parsing in core.
  • Event types are inferred from what arrives: the signature inference, type proposals and overlap refusal in internal/domain/eventtype move into the events module's unmatched groups.
  • The CEL environment in internal/domain/eda/expr moves into triggers for when and for mapping event fields onto workflow inputs, replacing bindings, mappings and playbook args.
  • Archie proposes the trigger and its mapping from an unmatched group as a draft, with a dry run (#2008); a person reviews and publishes, or writes one directly. One write path for both.

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 when and input mapping feed a workflow's inputs, and once published the next payload starts a run with those inputs.

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 `when` conditions and `args`. 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: - Any sender gets a generated endpoint with its own token or signing scheme (#2021), and a generic webhook connector stores any JSON body as the event, with no vendor parsing in core. - Event types are inferred from what arrives: the signature inference, type proposals and overlap refusal in `internal/domain/eventtype` move into the events module's unmatched groups. - The CEL environment in `internal/domain/eda/expr` moves into triggers for `when` and for mapping event fields onto workflow inputs, replacing bindings, mappings and playbook `args`. - Archie proposes the trigger and its mapping from an unmatched group as a draft, with a dry run (#2008); a person reviews and publishes, or writes one directly. One write path for both. 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 `when` and input mapping feed a workflow's inputs, and once published the next payload starts a run with those inputs.
sam added the featurehigh labels 2026-11-16 10:11:02 +00:00
sam added a new dependency 2026-11-16 10:11:12 +00:00
sam added a new dependency 2026-11-16 10:11:16 +00:00
Author
Owner

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.

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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#2032