Does n8n support human-in-the-loop interactions in workflows?

Below is an overview of two approaches you can take within n8n to introduce a human-in-the-loop mechanism that pauses workflow execution until you receive external input:

---

1. Using the Wait Node

n8n provides a Wait node that lets you pause your workflow mid-execution. With this node you can either:

• Wait for a predetermined duration before proceeding.
• Wait until a specific event occurs, such as a webhook call.

By configuring the Wait node to resume execution when, for example, a human submits an approval or additional data through a webhook, you can effectively integrate human input in your automated process.

---

2. Implementing a Human Fallback Workflow

There is also a common pattern used in n8n that involves creating a human fallback workflow. In this approach:

• The main workflow uses automation (for example, using a Chat Trigger and an Agent) to address the user query.
• If the AI or automated part cannot adequately handle the query, the workflow then calls a secondary workflow.
• The secondary workflow is designed to send a notification (such as a Slack message) to a human operator, requesting intervention.
• Once the human provides the required input (e.g., via a designated form or reply), the process continues.

This pattern not only pauses the automated execution but also routes the workflow for human assistance when needed.

---

Summary

Yes, n8n can support a human-in-the-loop mechanism. You can pause a workflow by:

• Using the Wait node to delay the workflow until external input (like a webhook call) is received.
• Leveraging a human fallback workflow to trigger human assistance when automated logic is insufficient.

Both methods ensure that workflows can safely and effectively request external input before proceeding with further steps.

For additional guidance and examples, please refer to the relevant n8n documentation pages on Waiting and Human Fallback for AI workflows.