Environment
Where the workflow runs
Timeout
How long an execution may take
Global rules
Instructions every node receives
Environment
Choose Browser for a Chromium web browser, or Linux or Windows for a full desktop. The environment decides which capabilities each Agent node can use. See Environments and What a node can do.Timeout
Timeout (minutes) accepts1 to 120.
It is the maximum time an execution may take. An execution that passes the limit ends as failed, or as cancelled with the reason timeout. See Executions and statuses.
Global rules
Global rules are instructions that apply across the whole workflow rather than to one node. Every Agent node receives them alongside its own instructions. Put guidance here when it should hold everywhere:- tone and formatting conventions
- sites or actions to avoid
- how to handle a blocker that can appear at any point in the execution
{{.variable}} templating as node instructions, so they can read the workflow’s inputs.
See Write good instructions for how to phrase them.
Workflow management
The same panel holds the controls for the workflow as a whole.Name and organization
Name and organization
Change the display name of the workflow.Set the organization that owns it. Anyone with access to that organization can see and run the workflow.
Clear browser cache
Clear browser cache
Clear the browser cache held by the profile this workflow uses. This removes:
- cached data and files
- stored cookies and sessions
- browser state and preferences
Delete workflow
Delete workflow
Delete the workflow for good. This removes every version, the whole execution history, and all associated data.
What lives elsewhere
Credentials, two-factor secrets, cookies, proxy settings, cache persistence and the inbox belong to an agent profile. A profile is reusable, so several workflows can share one.Agent profiles
Credentials, cookies and proxy settings
Environments
Browser, Linux and Windows

