Skip to main content

​
Overview

When building or troubleshooting a workflow, you often want to confirm it behaves as expected before activating it for live events. Manual Run lets you trigger a workflow execution on demand, with full control over the input data. This is a real execution — it runs all nodes, processes data, and produces results just like an automatic trigger would.
Manual Run is available on supported plans. If the Manual Run button appears disabled, it may be gated by your current plan’s workflow execution quota.

​
How to Use Manual Run

​
Step 1: Open the Workflow Builder

  1. Navigate to Settings → Workflows
  2. Open the workflow you want to test

​
Step 2: Ensure the Workflow is Deployed

The workflow must be Deployed (not just saved as a draft) before you can run it manually. If you see unsaved changes, click Deploy to publish the latest version first.

​
Step 3: Click “Manual Run”

In the top-right area of the workflow builder, click the Manual Run button.

​
Step 4: Provide Input Data

A modal will appear prompting you to fill in the trigger’s input data. There are two ways to enter it:
ModeHow It WorksWhen to Use
FieldsA form with individual fields for each expected inputEasier for most users — fill in values one by one
JSONA raw JSON text area for the full payloadUseful when you have a payload ready to paste, or when testing complex nested data
Fill in values for the fields that matter to your workflow — at minimum, any fields your action nodes reference via variables.

​
Step 5: Review the Run

Click Run to execute the workflow. Once complete, switch to the Runs tab to see the result. You can inspect each individual node — its inputs, outputs, and status — to confirm everything worked as expected.

​
What Manual Run Actually Does

Manual Run is a full, live execution of your workflow. This means:
  • Records will be created or updated if your workflow includes Create Record or Update Record nodes
  • Emails and Slack messages will be sent if your workflow includes notification nodes
  • Contacts will be enrolled in sequences if your workflow includes an Add to Sequence node
  • HTTP requests will be fired if your workflow includes a Send HTTP Request node
If you only want to validate the workflow’s structure without executing real actions, use the Deploy Checklist validation in the builder instead.
Manual Run executes against live data. Use test records or a sandbox environment if you want to avoid making real changes during testing.

​
Troubleshooting / FAQs

Two possible reasons: (1) Your workflow hasn’t been deployed yet — click Deploy first. (2) Your plan’s workflow execution quota has been reached. Check your Settings → Usage page to review your current quota.
Deploy publishes your latest workflow version so it goes live for future trigger events. Manual Run actually executes the workflow right now, with input data you provide. You need to deploy before you can manually run.
Open the Runs tab and click into the run. Expand each node to inspect its inputs and outputs. Look for variables that resolved to empty or unexpected values — this usually means a variable reference is pointing to a field that wasn’t populated in your test input, or that a Find Records node returned no results.
Yes. You can manually run a workflow regardless of whether it is Active or Inactive, as long as it has been deployed. Manual runs are independent of the Active/Inactive toggle — that toggle only controls whether the workflow fires automatically from its trigger.
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.