Quick Answer: What is the Manual Trigger Node?

[!NOTE] The Manual Trigger Node is an interactive entry point that allows you to start a workflow execution on-demand. Unlike automatic triggers (Schedule or Webhook), the Manual Trigger is designed for testing and for applications where a user must explicitly click "Run" to begin the document pipeline.

Core Capabilities

1. Interactive Testing

When building a complex pipeline, use the Manual Trigger to step through your nodes one-by-one without waiting for an external event (like an email or webhook).

2. Static Data Injection

You can define hardcoded field values in the Manual Trigger properties. Downstream nodes can reference these via {{manual_trigger_id.my_field}}. This is useful for testing logic branches (e.g., forcing a value to $1,000 to test an "If-Else" node).

3. "Run Locally" Integration

In the Workflow Editor, clicking the Global Run button defaults to the Manual Trigger if no other trigger is provided with data.

Configuration Guide

Field	Description	Type
Label	Custom name for the trigger.	String
Initial Data	Key-value pairs of static data.	JSON Object

Best Practices

Testing Anchor: Always keep a Manual Trigger on your canvas during the development phase. You can have multiple triggers; the engine will simply use the one you click to launch.
Swap for Production: Before deploying your Final Workflow, remember to swap or add an Automatic Trigger if the workflow is meant to run without human intervention.

[!TIP] Need to upload files during your manual run? The manual execution panel will automatically prompt you for files if your workflow contains a File Input Node.