Collect data for your workflow with Human in the Loop
- 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 Collect Data action pauses your Zap run so you can ask for more information from one or more reviewers. You can then map that data to later steps in your Zap. With the Collect Data action, you can send review notifications to your email, Slack account, or to another Zap so you can receive notifications via any other app available 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.
- You must share this Zap with your designated reviewers so they have access to this Zap.
- The Trigger a Zap notification method requires a second Zap that uses the Human in the Loop New Approval Requested trigger.
1. Add a Human in the Loop action
Start by adding a Collect Data action to your Zap.
- In the Zap outline, select the Action step or click the plus sign + to add a new action. 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 Action event field to open the dropdown menu.
- Select Collect Data.
- Click Continue. This will open the Configure tab.
2. Configure your Collect Data action
Action configuration section
In this section, you can define what data you want to collect.
- In the Data collection message field, enter a message or map a field from a previous step.
- Use this field to explain that you want more information from your reviewer before the Zap continues.
- In the Data inputs field, click + Add field. A dropdown menu will appear.
- Use this field to collect specific data from your reviewer.
- Each time you finish creating a data input, a new input box will appear so you can add more, if needed.
- In the Field name field, enter a name for your input field.
- Click the Field type field to open the dropdown menu, then select a field type option.
- Use this field to limit what kind of information the reviewer can enter. The reviewer will have to enter data that matches the field type.
- For example, reviewers will only be able to enter email addresses in an “email” field type.
- In the Is this data input field required? field:
- If you click to toggle the switch on, the reviewer must respond to this field.
- If you leave the toggle switch off, the field will be optional.
- (Optional) Click + Add field and repeat the process for each additional input field you want to add.
You can map fields from your Collect Data action configuration section to later steps in your Zap.
- Your Data inputs fields will appear as “Submitted Content {field name}”, where “{field name}” is the name of the fields you created in the Data input field.
- For example, if you have a field called "Numerical accuracy", it will appear as "Submitted Content Numerical accuracy" when you map it.
- By default, the Collect Data action will include an optional Additional notes field.
- Reviewers can add notes using this field.
- In the results of the Zap step, this will appear as the field “Reviewer Note”.
Notification section
In this section, you can define how your reviewer is notified of a data collection request.
- Click the arrow icon to expand the Notification section.
- In the Send to field, click to open the dropdown menu, then select an option:
- Email.
- Slack.
- Trigger a Zap.
- Additional fields specific to each option will appear.
- In the Email recipients field, enter an email address.
- This is the email address that Human in the Loop will send the notification to.
- Each time you finish entering an email address, a new input box will appear. Use it to add more recipients, if needed.
- In the Send Preview field, you will see the email address associated with your Zapier account.
- Click Send a preview to send a preview email to yourself.
- You cannot change this value.
Slack
- In the Account field, select a Slack app connection or connect a new Slack account.
- In the Message Type dropdown menu, select either:
-
Channel: notify a specific Slack channel. The Channel field will appear.
- Click to open the dropdown menu.
- Select a Slack channel.
-
User: notify a specific Slack user. The Slack recipient field will appear.
- Click to open the dropdown menu.
- Select a Slack user.
- Each time you finish entering a channel or user, a new input box will appear. Use it to add more, if needed.
-
Channel: notify a specific Slack channel. The Channel field will appear.
Trigger a Zap
If you want to trigger another app for notification, you can use the Trigger a Zap option. You must first create that second Zap, then complete its trigger app and event setup and configure the trigger step. Once that’s done, return to your Collect Data step and:
- Click the Triggered Zap field to open the dropdown menu.
- Select a Zap that uses the New Approval Requested trigger.
- (Optional) 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 this 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.
- (Optional) Click + Add Triggered Zap to add more Zaps that will trigger when this action step runs.
When you use the Trigger a Zap notification option:
- Include enough information about the Zap run, like the Zap URL, so reviewers can easily find the right notification to review.
- You can pair the trigger with any app on Zapier to receive the notification. Some examples of how to collect notifications:
- In a table using Zapier Tables. Create a new row with each new notification. Users can review one or more notifications at their own pace.
- In a project management tool like Jira. Users can triage tickets during their existing development processes.
- In a customer relationship management app like HubSpot. Users can review from within a customer’s deal.
Reviewer section
In this section, select who will review the Zap run and what to do if the reviewer does not respond in time.
- Click the arrow icon to expand the Reviewer section.
- In the Reviewers field, click to open the dropdown menu.
- Select a Zapier user from your account.
- Each time you finish selecting a user, a new input box will appear so you can add more reviewers, if needed. Only one user can complete a review.
- In the On timeout field, click to open the dropdown menu and select an option:
- Skip and continue: if the user does not review in time, the Zap will continue running without a response.
- End run: if the user does not review in time, the Zap will stop running.
- In the Timeout value field, enter a number.
- This is the numerical value for how long the Zap will pause at the Human in the Loop step while waiting for the reviewer to take action.
- The minimum value is 1.
- In the Timeout unit field, click to open the dropdown menu, then select an option.
- Minutes.
- Hours.
- Days.
- Weeks.
- This is the unit of time for how long the Zap will pause at the Human in the Loop step while waiting for the reviewer to take action.
- In the Send reminder field, select either:
- Yes. Two more fields will appear.
- No.
- If you selected Yes:
- In the Reminder Value field, enter a number.
- This is the numerical value for how long the step will wait to send a reminder after the initial notification.
- In the Reminder Time Unit field, click to open the dropdown menu, then select an option:
- Minutes.
- Hours.
- Days.
- Weeks.
- This is the unit of time for how long the step will wait to send a reminder after the initial notification.
- In the Reminder Value field, enter a number.
- Click Continue. This will open the Test tab.
3. Test your step
- Click Test step.
Testing this step will not send a notification to reviewers. It will create sample fields and values that you can review and map to later steps in your Zap. If you want a preview notification, use the send preview feature in the Configure tab to send yourself an example notification. If you prefer a live test with real data, you can test the run end to end instead.
Additional info
- Only successful Human in the Loop actions will count toward your task usage.
- Previews and notifications sent by the action do not count as separate tasks.
- A Human in the Loop action can be the last step in a Zap, but Zapier recommends adding action steps afterwards to use its data.
- 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.
- Human in the Loop actions may display step run statuses specific to the review process.
- You can review Human in the Loop activities in the audit log.
- You can use Paths to set up an alternative workflow if a reviewer skips a request.
Limitations
- Reviewers must have a Zapier account.
- You must share this Zap with your designated reviewers so they have access to this Zap.
- If you're on a Pro account, you can only send requests to yourself.
- If you’re in a Team or Enterprise account, while you can send a notification to any email address, the reviewer(s) must be logged in as one of the Zapier users you select in the Notification section.
- You cannot add a Human in the Loop action within or after a Looping step.
Next steps
Once the Zap is published, when a Collect Data action runs, the reviewers you select will receive a request notification. It will include a link to the step that needs review. They must log into their Zapier account to review the request.
Learn more about: