Manual Trigger

Start a workflow manually from the editor or API

Node Type

Trigger

Icon

PlayCircle

Overview

The Manual Trigger node acts as the entry point when you click Run in the editor. It's perfect for building, testing, and running workflows on demand without external events.

Key Features

• On-demand execution from the UI
• No external setup required
• Optional initial payload for downstream nodes

Prerequisites

Workflow Access

Ability to open and run workflows from the builder

Manual access to the workflow in the editor

Optional: API access to start runs programmatically

Technical Requirements

System capabilities needed for manual triggering

Trigger Mechanism: System capable of starting workflows on demand

Optional Payload: Ability to provide initial data at run start

Node Configuration

Optional Fields

Initial Data

Type:JSON

Required:No

Value Type:object

Optional JSON payload you can pass when starting a run manually. This data is made available to downstream nodes as the workflow begins.

Technical Details

Trigger Execution

How the manual trigger starts a workflow run

Manual Start

Like all trigger nodes, the Manual Trigger cannot be executed as part of a workflow graph. It acts as the starting point for a run initiated from the editor or an external call.

Execution Metadata

When a run begins, the trigger provides execution metadata such as start time and any initial payload. Downstream nodes can read this data to tailor their behavior.

Example: Starting with Payload

Passing initial data when running a workflow

{
  "initialData": {
    "userId": "abc_123",
    "mode": "test"
  }
}

If supported by your environment, you can attach an initial JSON payload when starting the run. The Manual Trigger exposes this payload to the rest of the workflow.

Examples & Use Cases

Ad-hoc Data Processing

Run workflows on demand for one-off tasks

Use Case

Quickly execute a workflow to process a single file, send a test email, or verify logic without setting up a schedule or webhook.

Configuration

{
  "initialData": { "task": "process-once" }
}

Debugging & Development

Iterate quickly during workflow design

Workflow Structure

▶️ Manual Trigger → 🧪 Experimental Node → 🔄 If-Else → 📤 Output

Tips

Use small payloads for quick iterations
Combine with If-Else to route test scenarios
Swap in real triggers (Schedule/Webhook) when ready

Best Practices

Do's

• Start simple workflows here before adding other triggers
• Pass minimal, well-structured initial data
• Log execution timestamps for traceability
• Transition to Webhook/Schedule when automating

Don'ts

• Don't rely on manual runs for production automation
• Avoid very large payloads at start time
• Don't skip error handling in downstream nodes

💡

Pro Tip: Use the Manual Trigger during early development to iterate rapidly. Once your flow stabilizes, switch to Schedule or Webhook to automate execution.