Skip to main content

Running Workflows

Once your workflow has at least one block and is saved, you can run it. This page covers running it yourself and the different ways a workflow can start.


Running It Yourself

  1. Open the workflow in the editor
  2. Click Run in the side panel (or press Ctrl/Cmd + Enter)

You'll see Run started — see it in the Logs tab. The run continues in the background, so you can keep working.

info

Run is only available when the workflow is saved and has at least one block. If it's greyed out, the button tells you why (e.g. "Save your changes first").


Providing Inputs

If your trigger block defines input fields, those values are used as the run's starting data. Blocks later in the flow can reference them. Set test values on the trigger block before running.


Watching a Run

While a run is in progress, a status strip shows its state — Queued, Running, Completed, Failed, Cancelled, or Paused — along with how many steps have run and the total time.

  • Stop — cancel a running workflow
  • Resume — continue a paused run (for example, after providing a missing connection)

For full detail, open the Logs tab — see Logs.


Ways a Workflow Can Start

TriggerHow It Starts
Start (manual)You click Run in the editor
ScheduleRuns automatically on a recurring schedule — see Schedules
WebhookRuns when an external service sends it a request
Chat TriggerRuns from a conversation with an AI assistant
API TriggerRuns when called from an external request

Add the trigger you want as the first block in your flow.


Running from Chat

If a workflow has a Chat Trigger, you can start it right from a conversation:

"Run the weekly sales report workflow"

The assistant shows a confirmation card with the workflow name and any inputs. Nothing runs until you click Approve.

caution

A workflow can only be started from chat if it has a Chat Trigger and your admin has allowed it. You always confirm before it runs.


Webhook Triggers

A Webhook block gives your workflow a unique web address. When an outside service sends a request to that address, the workflow runs.

  • Copy the generated webhook address from the block's settings
  • A signing secret is shown once when created — copy it right away
  • You can pause a webhook to stop accepting requests, or rotate its secret

Tips

  • Test with the Run button before relying on a schedule or webhook
  • Check the Logs tab after each run to confirm it did what you expected
  • Name your steps clearly so run logs are easy to follow