How to Run n8n Workflows Manually

Navigate to your n8n instance and open the workflow you want to test. The workflow editor shows all your nodes connected by lines representing data flow. You do not need to activate the workflow to run it manually. In fact, it is best practice to test with manual execution before activating any workflow. Make sure all nodes are fully configured with the required credentials and parameters.

Look for the Execute Workflow button at the bottom of the editor canvas. It is a large button with a play icon. Clicking it runs the entire workflow from the first trigger node through every connected node. During execution, each node highlights in sequence, and you can see the status change from waiting to running to success or error. If any node fails, execution stops at that node and shows the error message.

If your workflow does not have a trigger node, or if you want a dedicated manual start point, add a Manual Trigger node. Click the plus button on the canvas, search for Manual Trigger, and add it as the first node. Connect it to the rest of your workflow. The Manual Trigger node produces a single empty item when executed, which starts the data flow through subsequent nodes. This is useful when your workflow normally uses a Schedule Trigger or Webhook but you want to test it without waiting.

1// Manual Trigger node configuration
2// No parameters needed — it fires a single empty item
3// Node type: n8n-nodes-base.manualTrigger
4// Connect its output to the first processing node

After a manual run, click on any node to see its output data. The output panel shows the JSON data that the node produced, along with the number of items. Use the Table and JSON tabs to switch between a formatted table view and raw JSON. This is the primary way to debug data transformation issues. Check that field names, data types, and values match your expectations at each step in the workflow.

When testing a workflow manually, the trigger node may produce different data each time. To get consistent test results, pin data on a node. After a successful execution, click on the node, then click the pin icon in the output panel. Pinned data is saved with the workflow and replayed on every subsequent manual execution instead of fetching live data. This saves API calls and gives you a stable dataset for testing downstream nodes.

1// Example: pin this sample data on a trigger node
2// Click the pin icon after seeing this output
3[
4  {
5    "json": {
6      "id": 1,
7      "name": "Test User",
8      "email": "test@example.com",
9      "status": "active"
10    }
11  }
12]