How to run n8n workflows manually?

To run n8n workflows manually, you can use the "Execute Workflow" button in the workflow editor, trigger them via webhooks, use the API endpoints, or schedule them for one-time execution. Manual execution allows you to test workflows during development or run on-demand processes without waiting for automatic triggers.

 

A Comprehensive Guide to Running n8n Workflows Manually

 

Step 1: Understanding Manual Workflow Execution in n8n

 

Before diving into the methods of running workflows manually, it's important to understand what manual execution means in n8n:

• Manual execution allows you to run workflows on-demand rather than waiting for triggers or schedules
• It's useful for testing workflows during development
• You can provide test data when executing manually
• Manual execution can bypass regular trigger nodes

n8n offers several methods to run workflows manually, each suited for different scenarios and use cases.

 

Step 2: Running a Workflow Using the Execute Workflow Button

 

The simplest way to run a workflow manually is using the Execute Workflow button in the n8n editor:

• Open your n8n instance (typically at http://localhost:5678 if running locally)
• Navigate to the Workflows section in the left sidebar
• Open the workflow you want to run
• Click the "Execute Workflow" button in the top-right corner of the editor

This method instantly runs the entire workflow from start to finish and shows the execution results in real-time.

 

Step 3: Executing from a Specific Node

 

Sometimes you may want to run only a portion of your workflow:

• Open your workflow in the editor
• Right-click on the specific node where you want to start execution
• Select "Run" from the context menu

This will execute the workflow starting from that specific node, which is useful for testing complex workflows in segments.

 

Step 4: Using Test Data for Manual Execution

 

When running workflows manually, you can provide test data:

• Open your workflow in the editor
• Click on the node where you want to inject test data
• Go to the "Test & Workflow Data" tab in the node editor panel
• Click "Run with test data" and enter your JSON test data

For example, if you're testing an HTTP request, you might use:

{
  "data": {
    "name": "Test User",
    "email": "[email protected]"
  }
}

This allows you to simulate specific data scenarios without needing actual trigger data.

 

Step 5: Running Workflows via Webhook Triggers

 

If your workflow contains a Webhook node, you can manually trigger it by making an HTTP request:

• Add a Webhook node as the first node in your workflow
• Configure the Webhook node (method, path, etc.)
• Save and activate your workflow
• Copy the Webhook URL displayed in the node
• Use a tool like curl, Postman, or your browser to make a request to that URL

For example, with curl:

curl -X POST -H "Content-Type: application/json" -d '{"data": "test"}' https://your-n8n-instance.com/webhook/path

This method is useful for integrating with external systems or for triggering workflows from scripts.

 

Step 6: Manual Execution via the n8n API

 

n8n provides a REST API that allows you to trigger workflows programmatically:

• Ensure your workflow is active and has an ID (save it if needed)
• Note your workflow ID (visible in the URL when editing the workflow)
• Use the API endpoint to trigger execution

Here's how to execute a workflow using the API with curl:

curl -X POST \\
  http://your-n8n-instance.com/api/v1/workflows/1/execute \\
  -H 'X-N8N-API-KEY: your-api-key' \\
  -H 'Content-Type: application/json' \\
  -d '{
    "workflowData": {
      "startNodes": ["Start"],
      "destinationNode": "End",
      "executionMode": "manual"
    }
  }'

Replace:

• 1 with your workflow ID
• your-n8n-instance.com with your n8n host
• your-api-key with your n8n API key
• Modify the startNodes and destinationNode based on your workflow

 

Step 7: Executing Workflows with n8n CLI

 

You can use the n8n command-line interface to run workflows:

• Ensure n8n is installed globally or accessible in your environment
• Use the execute command with your workflow ID or file path

For workflows saved in your n8n instance:

n8n execute --id=1

For workflows saved as JSON files:

n8n execute --file=/path/to/workflow.json

This method is particularly useful for server environments or scheduled tasks.

 

Step 8: Creating a Manual Trigger Node

 

The Manual Trigger node is specifically designed for workflows that need manual execution:

• Create a new workflow or edit an existing one
• Add a "Manual" trigger node as the first node in your workflow
• Configure the rest of your workflow as needed
• Save the workflow

When you want to run the workflow:

• Open the workflow in the editor
• Click the "Execute Workflow" button

The Manual trigger node can also be configured to accept input parameters, making it versatile for different execution scenarios.

 

Step 9: Scheduling One-Time Executions

 

For workflows that need to run once at a specific time:

• Add a "Schedule Trigger" node as the first node
• Configure it for a single execution
• Set the date and time for execution
• Save and activate the workflow

Configuration example:

• Mode: Single
• Date & Time: [your specific date and time]

This method is technically an automated execution, but it's useful for planned one-time manual operations.

 

Step 10: Using the Execute Workflow Node

 

You can run workflows from within other workflows:

• Add an "Execute Workflow" node to your primary workflow
• Select the workflow you want to execute
• Configure any input data you want to pass
• Run the primary workflow manually

This is powerful for creating modular workflow systems where you manually trigger a master workflow that executes several sub-workflows.

 

Step 11: Passing Data to Manual Executions

 

When executing workflows manually, you might want to pass specific data:

• For API executions, include the data in the request body
• For webhook triggers, send the data as part of the webhook payload
• For the Execute Workflow button, you can use the "Test & Workflow Data" tab

Example of passing data via the API:

curl -X POST \\
  http://your-n8n-instance.com/api/v1/workflows/1/execute \\
  -H 'X-N8N-API-KEY: your-api-key' \\
  -H 'Content-Type: application/json' \\
  -d '{
    "data": {
      "customer": {
        "id": 12345,
        "name": "Example Customer"
      }
    }
  }'

This allows you to provide context-specific information during manual execution.

 

Step 12: Monitoring Manual Executions

 

After manually triggering a workflow, you can monitor its execution:

• Navigate to the "Executions" tab in the n8n interface
• Find your workflow execution in the list
• Click on it to see detailed execution information
• Examine the input/output for each node
• Check for any errors or warnings

This helps in debugging and understanding the workflow's behavior during manual runs.

 

Step 13: Setting Up Error Handling for Manual Executions

 

For more robust manual workflows, configure error handling:

• Add an "Error Trigger" node to your workflow
• Connect it to nodes that should run when an error occurs
• Set up notification nodes (e.g., Send Email, Slack) to alert about errors

This ensures you're notified if something goes wrong during manual execution, which is especially important for critical workflows.

 

Step 14: Using Environment Variables with Manual Executions

 

When running workflows manually in different environments:

• Set up environment variables in your n8n instance
• Use these variables in your workflow nodes
• When executing manually, the workflow will use the current environment configuration

This allows the same workflow to behave differently based on the environment, without changing the workflow itself.

 

Step 15: Best Practices for Manual Workflow Execution

 

To ensure smooth manual executions:

• Always test workflows in a development environment first
• Document the steps for manual execution for team members
• Consider creating a "dry run" mode for complex workflows
• Log the results of manual executions for audit purposes
• Implement appropriate access controls for sensitive workflows

Following these best practices will help maintain workflow reliability and security, especially for critical business processes that require manual intervention.