Master n8n ManualTrigger Workflows: Step-by-Step Guide

If you're building automations in n8n but need human control over when they run, the manualTrigger node is your secret weapon. Unlike scheduled or event-driven triggers, manualTrigger lets you launch workflows instantly—with a single click. Whether you're approving invoices, testing integrations, or kicking off data syncs after validation, this guide shows you exactly how to use it effectively in 2026.

What Is the n8n ManualTrigger Node?

The n8n-nodes-base.manualTrigger is a core node in n8n that starts a workflow only when manually activated—either via the n8n UI, API call, or webhook. It requires no external event, timer, or condition to initiate execution. Think of it as the "start button" for your automation.

Unlike scheduleTrigger (which runs on timers) or webhook (which responds to HTTP requests), manualTrigger gives you full control. It’s ideal for processes where human judgment is required before proceeding.

Why Use ManualTrigger? Top 5 Use Cases

ManualTrigger isn’t just for testing—it powers real-world business logic. Here are proven scenarios:

1. Approval Workflows: Managers review expense reports → click “Approve” → trigger reimbursement via Stripe.
2. Data Validation: Import CSV → validate entries manually → trigger cleanup with set and if nodes.
3. Testing & Debugging: Run workflows on-demand during development without waiting for schedules.
4. Event-Driven Human Tasks: After a support ticket is marked “Resolved,” agent clicks to trigger follow-up email.
5. Batch Processing: Process 100+ records only after QA sign-off.

ManualTrigger vs. Other Triggers: Key Differences

Trigger Type	Initiation Method	Best For	Requires External Input?
manualTrigger	User click or API call	Human-in-the-loop, testing	No
scheduleTrigger	Time-based (cron)	Recurring tasks (daily reports)	No
webhook	HTTP POST request	Real-time events (form submissions)	Yes
awsS3	File upload to bucket	File processing pipelines	Yes

How to Set Up a ManualTrigger Workflow in n8n

Follow these 5 steps to build your first manualTrigger workflow:

Step 1: Create a New Workflow

In your n8n dashboard, click + New Workflow. Name it (e.g., “Expense Approval Flow”).

Step 2: Add the manualTrigger Node

Click the + button → search for “manualTrigger” → select n8n-nodes-base.manualTrigger.

Step 3: Configure Execution Options

By default, the node triggers when you click Execute Workflow in the UI. To allow API triggers:

• Enable “Execute via API” in node settings.
• Copy the generated webhook URL for external use.

Step 4: Add Action Nodes

Chain nodes after manualTrigger. Example flow:

1. manualTrigger → starts workflow
2. httpRequest → fetch pending expenses from Airtable
3. if → check if amount > $500
4. set → add approval timestamp
5. stopAndError → halt if invalid data

Step 5: Test & Deploy

Click Execute Workflow → verify logs → activate workflow.

Advanced: Chaining manualTrigger with Other Nodes

Unlock power by combining manualTrigger with core nodes:

Example: Approval + HTTP Request + Conditional Logic

Use case: Approve a marketing spend request.

1. User clicks Execute on manualTrigger.
2. httpRequest pulls request details from Notion.
3. if node checks budget availability.
4. If approved, set updates status; else, stopAndError alerts finance.

Debugging Tips

• Workflow not triggering? Check if “Execute via API” is enabled.
• Data missing? Use stickyNote to label data flow.
• Errors in chain? Add stopAndError after critical nodes.

Free Download: Basic manualTrigger JSON Template

Copy this JSON into n8n to get started instantly:

{
  "nodes": [
    {
      "parameters": {},
      "name": "manualTrigger",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [250, 300]
    },
    {
      "parameters": {
        "functionCode": "return [{ json: { message: 'Workflow started manually!' } }];"
      },
      "name": "set",
      "type": "n8n-nodes-base.set",
      "typeVersion": 1,
      "position": [450, 300]
    }
  ],
  "connections": {
    "manualTrigger": {
      "main": [[{ "node": "set", "type": "main", "index": 0 }]]
    }
  }
}

Tip: Import via n8n UI → Settings → Import from Clipboard.

Who Should Use manualTrigger?

• Developers: Test APIs without mock events.
• Operations Teams: Approve bulk actions (e.g., user deletions).
• Marketers: Launch campaigns after creative review.
• Small Businesses: Automate invoicing after manual checks.

When NOT to Use manualTrigger

Avoid manualTrigger if:

• Processes must run automatically (use scheduleTrigger).
• Real-time response is critical (use webhook).
• Fully autonomous pipelines are needed (e.g., IoT sensor data).

Tools & Integrations That Work With manualTrigger

Tool	Integration Method	Use Case
Slack	HTTP Request → Slack webhook	Notify team after manual approval
AWS S3	Upload file → trigger via API	Process documents post-review
Google Sheets	Read/write via n8n Google Sheets node	Update status after manual check
Zapier	Webhook → n8n API	Bridge non-n8n tools

Pricing: Is manualTrigger Free?

Yes—manualTrigger is a core n8n node and free to use in both:

• n8n Cloud: Free tier includes 2,500 workflow executions/month.
• Self-hosted: Completely free (MIT license).

No hidden costs. Scale as needed.

Local Experts: Hire an n8n Consultant

Need help building complex manualTrigger workflows? Our certified n8n experts offer:

• Custom workflow design
• Debugging & optimization
• Team training

Available globally — including London, Sydney, Toronto, and remote.