How can I determine the last executed node in a successful n8n workflow?

Below is an approach based on our documentation that might help you troubleshoot and identify the actual flow path your workflow took:

Use the Executions Log and Read-Only View

n8n lets you inspect each run in detail. To find the last executed node in a successful run, you can:

1. Open the Executions Log
   Click on Executions in the left-side panel. (See the Executions log documentation for details.)

2. View the Specific Execution
   For a selected run, click on the execution name or the View button. This opens the workflow in read-only mode so you can scroll through all the nodes in the order they were processed, along with their input and output data.

3. Identify the Final Node
   In the read-only execution view, examine the node sequence. The node that appears last represents the final branch taken during that particular execution. This might help you see which branch or node is being reached and verify if it’s the one you expected.

Adding Debugging Aids

If the graphical execution view isn’t enough, you can enhance your workflow with internal debug steps:

• Custom Logging:
  You might include a node (for example, a Function node) at the end of each branch to log details or even write data to external storage. This way, you can inspect the output for every branch to know which one was run.

• Stop and Error Node for Controlled Breaks:
  Although used primarily for error handling, the Stop and Error node can help you throw a controlled error if a certain condition isn’t met. This won't work for successful runs, but it can be handy if you want to explicitly mark when an unexpected branch is reached.

Summary

Right now, n8n doesn’t provide an automatic “last executed node” flag in the output when a workflow succeeds. Instead, you’ll need to use the detailed execution view to visually inspect which node was processed last. Adding your own logging within specific branches can also give you additional insights into the path taken by your workflow.

This approach is documented in the sections related to viewing executions in the workflow’s execution log and using the read-only execution mode to debug workflow outputs.