Trigger Zaps when Human in the Loop steps run
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
Table of Contents
Human in the Loop is a built-in tool that lets you pause a Zap at a certain step so a human can review before your workflow continues. Its New Approval Requested trigger allows you to send a custom notification from Human in the Loop to any other app on Zapier.
Available on plans:
Free
Professional
Team
Enterprise
Pre-requisites
- A paid Zapier account. Human in the Loop is a premium app on Zapier.
- Before you set up this Zap, you must have a first Zap set up with:
- A Human in the Loop Collect Data or Request Approval action.
- The action's notification section set up to trigger a Zap. Learn how to trigger a Zap in the Collect Data action and in the Request Approval action.
1. Trigger app and event setup
Start by creating a new Zap in your account home. You will connect this Zap to the first Zap mentioned in the pre-requisites section of this article.
- In the left sidebar, click + Create. A dropdown menu will appear.
- Select Zaps. You will be redirected to the Zap editor in a new browser tab or window.
- In the Zap outline, select the Trigger step. A dialog box will open.
- In the search box, search for and select Human in the Loop. The right sidebar will open to the Setup tab.
- Click the Trigger event field to open the dropdown menu.
- Select New Approval Requested.
- Click Continue. This will open the Configure tab.
Rename this Zap so it’s easy to find in the next step.
2. Configure both Human in the Loop Zaps
Configure the trigger step in the second Zap
In this Zap:
- (Optional) In the Input fields field, enter the name of fields you want to send data from in the corresponding Additional data field in the first Zap.
- These data fields can be mapped to later steps in this Zap.
- In the Configure tab, review the Zap selected in the Zap that initiates this workflow field to ensure it corresponds to the Zap that has the Human in the Loop action step.
- Click Continue to proceed to the Test tab.
The Zap that starts this workflow field is a view-only field. Once it is connected to the first Zap, you can only change the value in this field from the first Zap.
Configure the action step in the first Zap
Next, return to the first Zap that has the Human in the Loop Collect Data action or Request Approval action.
- In the Triggered Zap field, review the Zap selected to ensure it corresponds to the Zap with the Human in the Loop trigger step.
- In the Additional data field, there will be new fields corresponding to the Input fields fields in your second Zap that triggers from this action step. Each has two columns:
- The first column is the name of the field. It corresponds with the values in the Input fields fields in your second Zap that triggers from this action step.
- In the second column, enter a value. This is the data the first Zap will send when it triggers the second Zap. This becomes a field that you can map to later steps in the second Zap.
You can trigger the same Zap from multiple Human in the Loop actions. They will have the same fields in the Additional data field in the action step as well as in the Input fields field in the trigger step.
For example, if you have 3 different Zaps with Human in the Loop actions that include a timestamp, enter “Timestamp” in the Input fields field of your trigger step. Then, in each of your three action steps, a “Timestamp” field will appear in the Additional data field.
Finish setting up those fields by entering values in the second column of those fields. Then, you will be able to map the timestamp field to later steps in the Zap. When the Human in the Loop trigger fires, the Zap will send the value of the “Timestamp” field to the trigger step regardless of which of the 3 Human in the Loop actions triggered it.
3. Test your trigger
- Return to the second Zap that has the New Approval Requested trigger.
- In the Test tab, click Test trigger. The Zap will load the newest records from the Zap you want to trigger from.
- You can then review and map fields from the trigger step to later steps in your Zap.
Next steps
Add action steps to map your trigger fields to. For example, you can:
- Use the review data to update a ticket in your project management app.
- Add a comment to a customer support ticket.
- Create a note in a deal in your customer relationship management app.