Collected sources and patterns will appear here. Add from search or the patterns library.
(NodeSchema, UserInput) -> HydratedExecutionContext
Collect required variables (secrets, files, options) from a user input schema defined on a workflow node and inject them into the execution context right before the node runs.
Problem it solves
Automated agent steps fail when they need environment variables or local files that the agent does not have access to ahead of time.
Consumes
Emits
The real projects this mechanism was found in. Attribution is the point — this is how the best teams actually do it.