A binding can't pass mapped values as a workflow's inputs #2116

Open
opened 2026-11-22 00:48:35 +00:00 by sam · 0 comments
Owner

Why: since #2062, a trigger can map event fields, but runs.CheckTrigger refuses any workflow with required inputs, so mapped values only reach the run as input.mapped.*. A workflow that declares inputs can't be started by a binding.

Done when: a trigger names which mapped fields fill which workflow inputs, CheckTrigger accepts a workflow whose required inputs the binding supplies, and a missing input is refused when the binding is saved, not at run time.

**Why**: since #2062, a trigger can map event fields, but runs.CheckTrigger refuses any workflow with required inputs, so mapped values only reach the run as input.mapped.*. A workflow that declares inputs can't be started by a binding. **Done when**: a trigger names which mapped fields fill which workflow inputs, CheckTrigger accepts a workflow whose required inputs the binding supplies, and a missing input is refused when the binding is saved, not at run time.
sam added the featuremedium labels 2026-11-22 00:48:35 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#2116