Manual Trigger
The Manual Trigger block enables you to start a workflow on demand with a single click in the user interface, offering a simple way to test or run processes manually.
Quick Start: The Manual Trigger requires no configuration. Simply drag it onto your canvas and click to run your workflow instantly.
Key Features
- One-Click Execution: Start workflows instantly from the UI without any external dependencies
- Zero Configuration: Ready to use immediately with no setup required
- Perfect for Testing: Ideal for validating workflow logic during development
- Debug-Friendly: Easily troubleshoot issues by running workflows on demand
- Ad-Hoc Processing: Execute workflows whenever needed without scheduling
Configuration
| Parameter | Type | Required | Description |
|---|---|---|---|
| Label | String | No | Custom display name for the trigger block |
| Description | String | No | Optional description for documentation purposes |
The Manual Trigger is the simplest trigger type - it requires no additional configuration beyond placing it on your canvas.
Setup Guide
Step 1: Add the Manual Trigger Block
- Open your workflow in the editor
- Navigate to the Triggers section in the block palette
- Drag the Manual Trigger block onto your canvas
- Position it as the starting point of your workflow
Step 2: Connect to Next Blocks
- Click on the output handle of the Manual Trigger
- Drag a connection to your next workflow block
- The workflow will execute this path when triggered
Step 3: Test Your Workflow
- Click the Run or Test button on the Manual Trigger block
- Observe the workflow execution in real-time
- Check the logs for any errors or unexpected behavior
Example Usage
Testing a New Workflow
Manual Trigger → Process Data → Send Email → Log ResultUse the Manual Trigger to test each step of your workflow before deploying to production.
One-Time Data Migration
Manual Trigger → Fetch Old Data → Transform → Insert to New DatabasePerfect for data migration tasks that only need to run once.
On-Demand Report Generation
Manual Trigger → Query Database → Generate Report → Export to PDFGenerate reports whenever needed without waiting for a schedule.
Debugging Complex Workflows
Manual Trigger → Condition Check → Branch A or Branch B → CompleteStep through your workflow logic to identify and fix issues.
Node Display
The Manual Trigger block displays:
- Label: Shows "Manual Trigger" or your custom label
- Status Indicator: Shows ready, running, or completed states
- Run Button: Click to execute the workflow immediately
- Last Run: Timestamp of the most recent execution
Error Handling
| Error Type | Cause | Solution |
|---|---|---|
| Workflow Not Published | Attempting to run an unpublished workflow | Publish your workflow before manual execution |
| No Connected Blocks | Manual Trigger has no output connections | Connect the trigger to at least one subsequent block |
| Execution Timeout | Workflow takes too long to complete | Optimize your workflow or increase timeout settings |
| Permission Denied | User lacks permission to run the workflow | Contact your administrator for access rights |
Best Practices
-
Use for Development: Leverage Manual Triggers extensively during workflow development and testing phases
-
Add Descriptive Labels: Give your Manual Trigger a clear label that describes what the workflow does
-
Test Before Scheduling: Always test workflows manually before converting to scheduled or event-driven triggers
-
Document Usage: Add descriptions to help team members understand when and why to use the manual trigger
-
Monitor Execution: Check workflow logs after manual execution to ensure everything works as expected
-
Clean Up After Testing: Consider removing or disabling Manual Triggers in production workflows that should only run automatically
Pro Tip: Use the Manual Trigger in combination with test data to validate your entire workflow before connecting it to real data sources or automated triggers.