Workflow definition settings

Use workflow definition settings to decide how new workflow runs start, maintain shared values, or offer a reusable template to another account. These settings are separate from the tasks and routes drawn in GraphEditor.

A workflow definition is the saved instructions. A workflow run is one execution of those instructions. Turning on a trigger can create new runs; opening a task table or board only displays existing work.

Open the settings

1. Open Workflow definitions and select the definition you want to configure.

2. Save it first if it is new. Settings links are available after the first Save.

3. In the editor footer, open the arrow beside Save.

4. Choose Webhook settings, Schedule trigger, Variables, Share settings, Public launch settings, or Workflows.

You need permission to edit the definition to change its settings. For webhook and schedule execution, choose an active, unlocked user from the definition's organization. Changing these settings does not change that user's roles. Ask an administrator if the definition, user or settings action is unavailable.

Choose a published version when a trigger must keep using tested instructions. For webhook and schedule settings, leaving the version at Latest workflow definition version follows the latest saved definition, including its draft. That is useful while testing but can change the instructions used by later runs. The selected version must be enabled and valid when it starts.

Choose the setting or action

You want to	Read
Give someone a public form link	Public launch settings, including supported components, publication, privacy and files.
React to an event from another system	Webhook settings, including sender checks, request/reply examples and recovery.
Start regularly at a specified time	Schedule trigger, including UTC cron, execution users and queued starts.
Maintain values shared by runs	Variables, including JSON values, limits and the effects of updates.
Offer a reusable workflow to another account	Share settings, including publication, copied content and recipient setup.
Try a workflow yourself	Run in the editor menu. A configured Launch Page collects input; otherwise use the JSON launch form.
Check runs and results	Workflows. This is monitoring, not another trigger.
Wait inside an already-running workflow	A Wait task, not Schedule trigger.

Each settings article explains that screen's purpose, setup, result, limits and recovery. Public launch, authenticated starting and template sharing are different jobs: making a Page public or sharing a template does not grant workflow access.

Editor settings, Pages and monitoring

Use the editor's General, Launch Page, Error Handling, Versions and Vector Stores tabs for workflow-wide settings. Use a Simple task's Task processor tab to select the Page that participants use to complete that task. Page settings control layout and visibility, not workflow start or task-completion permission.

After any trigger change, start one controlled test, check Workflows, inspect its input and task results, then confirm the final outcome. Keep template sharing, public launch, authenticated starts and task lists distinct when checking access.