Running Your First Workflow

Learn the different ways to run a workflow and how to monitor its progress.

Overview

Once a workflow is saved, you can run it manually from the designer or the workflow list, or let a configured trigger fire it automatically. Each run becomes an Execution, which is logged step-by-step so you can see what happened, what data flowed through each node, and whether anything failed.

While iterating, manual runs from the designer are the fastest feedback loop. Once the design is stable, swap to an automatic trigger (Schedule, Webhook, or Email) so the workflow runs without you in the loop.

Before You Start

A saved workflow with a trigger and at least one downstream node.
Valid connections for every Connector node the workflow uses.
Enough credits on your plan to cover the run.

Ways to Run

From the Designer - click Run in the toolbar. Best for testing during development.
From the Workflow List - click the run icon on a workflow card on the Workflows page. Useful for ad-hoc runs without opening the designer.
Schedule trigger - the workflow fires on a recurring schedule (hourly, daily, custom cron) in the workspace timezone.
Webhook trigger - the workflow fires when an external system POSTs to your unique webhook URL.
Email trigger - the workflow fires when a new email arrives in the monitored inbox.
Manual trigger from outside the designer - any workflow with a Manual trigger can be run from the list view as well.

Monitoring Progress

While the run is in flight, nodes change colour: blue for running, green for success, red for error. Click a completed node in the designer to see its input and output data. The execution panel at the bottom of the designer streams step results as they complete.

Viewing Results

After the run finishes, open Executions from the sidebar to find it in the full history. Each execution row shows status, trigger type, start time, and duration. Click into a row for step-by-step inputs, outputs, errors, and timing.

Tips

Use Manual triggers while you iterate; switch to Schedule, Webhook, or Email once the workflow is stable.
Click a green node in the designer to copy its output - useful for shaping downstream node inputs.
If a run is stuck on a Human Approval step, head to Approvals to respond.

Common Pitfalls

Clicking Run after unsaved changes. The runner uses the saved definition, not the canvas state.
Running a workflow whose Connections have expired tokens - re-auth from the Connections page first.
Confusing the workspace timezone with your local timezone for Schedule triggers. Schedules use the workspace setting.

Learn More

Workflow execution documentation