Workflow file uploads and optional settings and connections

Over June we loosened what a workflow needs before it can run. It can take files as input, its settings can be optional, and so can its connections, so one workflow can serve people with different tool stacks and a missing nice-to-have no longer blocks a run.

File inputs

• An input marked as a file renders as an upload field on the run form, and the file lands in the workflow's workspace for code or agent steps to read. You can restrict the accepted type, such as PDF only.
• Multi-file fields accept several uploads at once.
• When the building agent tests a file input, it stages a real sample file, so tests match what real uploads do.
• Each run records the input it received alongside the trigger that fired it.

Optional settings and connections

• A setting with a default can be left blank, and the run uses the default.
• A connection can be marked optional: the workflow runs either way, skipping the dependent step when the account isn't connected. Optional connections are labeled in the workflow view and in templates.
• The building agent reserves optional connections for secondary paths, never for something the core flow depends on.

Also shipped

• Workflows with several triggers can tell which one fired.