Repository navigation
Workflow body parameters? #30047
Description
Activity
- locked and limited conversation to collaborators
on May 4, 2026 - unlocked this conversation
on May 4, 2026 - changed the title
[-]Workflow body configuration?[/-][+]Workflow body parameters?[/+]on May 4, 2026 @copilot update documentation FAQ on using workflow_dispatch inputs as parameters and env vars in prompt body.
- linked a pull request that will close this issueDocument workflow parameters in prompt bodies #66674
on Oct 7, 2026 Status (2026-10-07; Maintainer direction): In the October 7 discussion, a maintainer requested an FAQ update on using
workflow_dispatchinputs as parameters and environment variables in the prompt body. The next step is to document the supported pattern and clarify whether placeholder replacement occurs before the agent receives the prompt.
I want my workflow to be easily configurable. e.g. someone can take it, then change a branch name or repo name in one place, and it applies everywhere.
At the moment I'm doing that with env vars:
Then there is also a note in the workflow body, e.g.
Is there a better way to do this? Ideally the placeholder in the agent body would be replaced before it is send to the LLM, e.g.
Build a report for Contosoand notBuild a report for ${PRODUCT}.It's not clear to be whether env vars do that today or not. I want them replaced before the agent is called so replacement is deterministic.