How to view execution history in n8n?

In n8n, you can view execution history by navigating to the Executions tab in the main interface. This tab displays a list of all workflow executions, including successful runs, errors, and manual triggers. You can click on any execution to see detailed information about what happened during that run, including input and output data for each node.

 

Step 1: Accessing the Executions Tab

 

To view the execution history in n8n, you first need to access the Executions tab:

1. Log in to your n8n instance.
2. In the main navigation menu on the left side of the screen, look for "Executions" and click on it.
3. This will open the Executions page, which shows a list of all past workflow executions.

The Executions tab is the central place where n8n logs every workflow run, whether it was triggered manually, by a schedule, or through a webhook.

 

Step 2: Understanding the Executions List

 

Once you're in the Executions tab, you'll see a list of all workflow executions with the following information:

• Status indicator (green checkmark for success, red X for errors)
• Workflow name
• Mode of execution (manual, production, etc.)
• Start time
• Duration
• Additional actions (like re-execute)

The executions are typically sorted with the most recent at the top. You can quickly identify failed executions by looking for red error indicators.

 

Step 3: Filtering Executions

 

The Executions list can become quite long if you have many workflows. To find specific executions:

1. Use the filter options at the top of the Executions page.
2. You can filter by:
   • Workflow (select from a dropdown of your workflows)
   • Status (All, Error, Success)
   • Date range
3. Apply your filters to narrow down the list of displayed executions.

Filtering is particularly useful when you're troubleshooting a specific workflow or looking for errors that occurred during a particular time period.

 

Step 4: Viewing Execution Details

 

To see detailed information about a specific execution:

1. In the Executions list, click on the execution you want to examine.
2. This will open the Execution Details view, which shows a visual representation of your workflow as it ran.
3. Nodes that executed successfully will be green, while nodes with errors will be red.
4. The execution path through your workflow will be highlighted, showing you the exact sequence of nodes that were processed.

This view gives you a high-level overview of how the execution proceeded through your workflow.

 

Step 5: Examining Node Data

 

To examine the data that passed through specific nodes during execution:

1. In the Execution Details view, click on any node in the workflow.
2. On the right side panel, you'll see tabs for "Input" and "Output" data.
3. The "Input" tab shows the data that entered the node.
4. The "Output" tab shows the data that left the node after processing.
5. If there was an error in the node, you'll also see an "Error" tab with details about what went wrong.

This is extremely useful for debugging as you can see exactly what data was available at each step of your workflow execution.

 

Step 6: Using JSON View and Table View

 

When examining node data, n8n offers different views to make data inspection easier:

1. In the Input or Output tab for a node, look for view toggle options (usually "JSON" and "Table").
2. JSON view shows the complete data structure in JSON format, which is helpful for seeing the exact data structure.
3. Table view displays array data in a more readable table format, which is useful for reviewing multiple items.
4. You can switch between these views depending on your preference and the type of data you're examining.

For complex data structures, the JSON view gives you the complete picture, while the table view makes it easier to scan through multiple items.

 

Step 7: Viewing Execution Context and Parameters

 

To see the overall execution context and parameters:

1. In the Execution Details view, look for "Execution Context" or similar options in the right panel.
2. This shows metadata about the execution, such as:
   • Execution ID
   • Start and end times
   • Trigger type
   • User who initiated the execution (if manual)
3. You may also see workflow parameters and variables that were used during this execution.

Understanding the execution context can help you identify patterns or issues related to specific trigger methods or times.

 

Step 8: Re-executing Workflows from History

 

n8n allows you to re-run workflows directly from the execution history:

1. In the Executions list, find the execution you want to re-run.
2. Look for a "re-execute" button or option (usually a play icon).
3. Click it to open the re-execution options.
4. You can choose to re-run the entire workflow or start from a specific node.
5. Confirm to begin the re-execution.

This feature is helpful when you've fixed an issue in your workflow and want to retry a previously failed execution without waiting for a new trigger.

 

Step 9: Downloading Execution Data

 

To save or share execution data:

1. In the Execution Details view, look for a download or export option.
2. This allows you to download the execution data as a JSON file.
3. The downloaded file includes all input and output data for each node, along with metadata about the execution.

Downloading execution data can be useful for:

• Sharing with team members for troubleshooting
• Keeping records of important executions
• Offline analysis of workflow performance

 

Step 10: Setting Up Execution History Retention

 

n8n allows you to configure how long execution history is retained:

1. Go to Settings or Configuration in your n8n instance.
2. Look for "Workflow Settings" or "Execution Settings."
3. Find options related to "Execution History" or "Execution Retention."
4. Configure the retention period based on your needs (e.g., 30 days, 90 days, etc.).
5. Save your changes.

Properly configuring retention settings helps manage database size while ensuring you have access to the execution history you need.

 

Step 11: Setting Up Error Notifications

 

To proactively monitor execution history for errors:

1. In n8n settings, look for "Notifications" or "Alerts."
2. Configure notifications to alert you when workflows fail.
3. You can typically set up email notifications or integrate with services like Slack.
4. Specify which workflows you want to monitor and what error conditions should trigger alerts.

Setting up notifications ensures you don't have to constantly check the execution history to catch errors.

 

Step 12: Using the API to Access Execution History

 

For advanced users, n8n provides API access to execution history:

// Example: Get all executions using the n8n API
// Replace YOUR_N8N_URL and YOUR_API_KEY with your actual values

fetch('YOUR_N8N_URL/api/v1/executions', {
  method: 'GET',
  headers: {
    'X-N8N-API-KEY': 'YOUR_API_KEY'
  }
})
.then(response => response.json())
.then(data => console.log(data))
.catch(error => console.error('Error:', error));

This approach allows you to:

• Integrate execution history into custom dashboards
• Perform automated analysis of workflow performance
• Build custom notification systems

 

Step 13: Troubleshooting Using Execution History

 

The execution history is a powerful troubleshooting tool. Here's how to use it effectively:

1. When a workflow fails, go to the Executions tab and find the failed execution.
2. Click on it to open the detailed view.
3. Look for red nodes that indicate where the error occurred.
4. Click on the error node to view the error message and the input data that caused it.
5. Use this information to diagnose and fix the issue in your workflow.

Common patterns to look for:

• Data format mismatches between nodes
• Missing required fields
• API rate limiting or authentication issues
• Timing problems with scheduled workflows

 

Step 14: Comparing Different Executions

 

To compare different executions of the same workflow:

1. Open the Executions tab and filter by the specific workflow.
2. Open two executions you want to compare (you may need to open them in different browser tabs).
3. Compare the input and output data at equivalent nodes.
4. Look for differences in the execution paths or data transformations.

This comparison can help identify why a workflow succeeds sometimes but fails in other cases.

 

Step 15: Managing Execution History in Self-Hosted n8n

 

If you're running a self-hosted n8n instance, you have additional options for managing execution history:

1. Access the database directly to query execution records.
2. Implement custom backup strategies for the n8n database to preserve execution history.
3. Modify configuration settings in your environment variables to change retention behavior.

For example, you can set the following environment variables:

# Set execution history to be kept for 60 days
N8N_EXECUTIONS_DATA_MAX_AGE=60

# Prune execution data automatically
N8N_EXECUTIONS_DATA\_PRUNE=true

# Set how often to prune (in seconds, default is 1 hour)
N8N_EXECUTIONS_DATA_PRUNE_INTERVAL=3600

These settings give you fine-grained control over how execution history is managed in your n8n instance.