Zapier Integration

Integrate HITL.sh with Zapier to connect human decision-making with over 7,000 apps and services. Perfect for teams who want powerful automation without writing code.

Before configuring Zapier, install the HITL.sh mobile app (App Store | Google Play) since it’s an integral part of the setup.

Zapier workflow with HITL.sh integration

Why Use Zapier with HITL.sh?

7,000+ App Integrations

Connect HITL.sh with popular tools like Gmail, Slack, Google Sheets, Airtable, and more

No-Code Automation

Build powerful workflows without writing a single line of code using visual interface

Multi-Step Workflows

Create complex automation sequences with conditional logic and multiple actions

Instant Setup

Get started in minutes with pre-built templates and intuitive configuration

Available Actions

HITL.sh provides two powerful actions in Zapier:

Create Request
Get Request Status

Create Request Action

Submit content for human review directly from your Zaps:

Use Cases:

Content moderation from form submissions
Approval workflows from CRM updates
Quality checks from data entries
Escalation from support tickets

Add HITL.sh Action

Search for “HITL.sh” and select “Create Request” action

Authenticate

Connect your HITL.sh account using your API key

Configure Request

Set up your request parameters

Create Request - Configuration in Zapier

Test & Activate

Test your Zap and turn it on to start automating

Supported Response Types

Configure how reviewers respond to your requests:

Text Response

Free-form text with character validation:Configuration:

{
  "response_type": "text",
  "response_config": {
    "placeholder": "Enter feedback...",
    "min_length": 10,
    "max_length": 1000
  }
}

Example Response: "The proposal looks solid but needs budget clarification in section 3."

Single Select

Choose one option from a list:Configuration:

{
  "response_type": "single_select",
  "response_config": {
    "options": ["Approve", "Reject", "Revise"]
  }
}

Example Response: "approve"

Multi Select

Choose multiple options:Configuration:

{
  "response_type": "multi_select",
  "response_config": {
    "options": ["Accuracy", "Tone", "Grammar", "Formatting"],
    "max_selections": 3
  }
}

Example Response: ["accuracy", "grammar"]

Rating

Numeric scale rating:Configuration:

{
  "response_type": "rating",
  "response_config": {
    "scale_min": 1,
    "scale_max": 5,
    "scale_step": 0.5
  }
}

Example Response: 4.5

Number

Numeric input with validation:Configuration:

{
  "response_type": "number",
  "response_config": {
    "min_value": 0,
    "max_value": 1000,
    "decimal_places": 2
  }
}

Example Response: 149.99

Boolean

Simple yes/no decision:Configuration:

{
  "response_type": "boolean",
  "response_config": {
    "true_label": "Approved",
    "false_label": "Rejected"
  }
}

Example Response: true

Request Configuration

Required Fields

Loop ID

string

required

The unique identifier of your HITL loop

Request Text

string

required

The content or question for reviewers

Response Type

select

required

Choose from: text, single_select, multi_select, rating, number, boolean

Response Config

object

required

Configuration object for your chosen response type

Optional Fields

Processing Type

select

default:"time-sensitive"

time-sensitive (urgent) or deferred (non-urgent)

Priority

select

default:"medium"

Priority level: low, medium, high, or critical

Timeout Seconds

number

Time limit before default response is used (60-86400 seconds)

Default Response

varies

Fallback value if request times out

Context

object

Additional metadata in JSON format

Status Codes

When retrieving request status, you’ll receive one of four status codes:

pending

Waiting for reviewer response

completed

Reviewer has submitted response

timeout

Request timed out, default response applied

cancelled

Request was cancelled before completion

Example Workflows

Content Approval from Google Forms

Automatically send form submissions for human review: Trigger: New Google Forms Response Action 1: HITL.sh Create Request

Loop ID: content_review
Request Text: {{Form Response}}
Response Type: single_select
Options: Approve, Reject, Needs Changes
Priority: high

Action 2: Send Email (based on response) Action 3: Update Google Sheet with decision

Slack Message Moderation

Monitor Slack channels and flag inappropriate content: Trigger: New Message Posted in Slack Filter: Message contains flagged keywords Action 1: HITL.sh Create Request

Request Text: Review this Slack message: {{Message Text}}
Response Type: single_select
Options: Allow, Remove, Warn User
Context: {"channel": "{{Channel}}", "user": "{{User ID}}"}

Action 2: Slack - Delete Message (if “Remove”) Action 3: Slack - Send DM to User (if “Warn User”)

Customer Refund Workflow

Handle refund requests with human oversight: Trigger: New Row in Airtable (Refund Requests) Filter: Amount > $100 Action 1: HITL.sh Create Request

Request Text: Refund request for ${{Amount}}
Reason: {{Reason}}
Customer: {{Customer Name}} ({{Customer ID}})
Response Type: single_select
Options: Approve Full, Approve Partial, Deny, Escalate
Priority: {{Amount > 500 ? "high" : "medium"}}

Action 2: Update Airtable with decision Action 3: Send confirmation email Action 4: Process refund (if approved)

Using Paths for Conditional Logic

Zapier Paths allow you to handle different response types:

├─ Path A: If response = "approve"
│  └─ Send approval email
│  └─ Update database status
│  └─ Post to Slack channel
│
├─ Path B: If response = "reject"
│  └─ Send rejection email
│  └─ Archive submission
│  └─ Log for review
│
└─ Path C: If response = "escalate"
   └─ Notify management
   └─ Create high-priority ticket
   └─ Send urgent Slack message

Best Practices

Test Thoroughly

Always test your Zaps with sample data before going live

Use Filters

Add filters to control when requests are created

Error Handling

Set up error notifications to catch failed Zaps

Monitor Usage

Track your Zapier task usage to stay within limits

Troubleshooting

Authentication Failed

Solution:

Verify API key is correct
Regenerate API key if needed
Check API key permissions in HITL dashboard

Invalid Loop ID

Solution:

Confirm loop exists in your HITL dashboard
Copy Loop ID directly from loop settings
Check for extra spaces in the field

Zap Not Firing

Solution:

Check trigger conditions are met
Verify Zap is turned ON
Review Zap history for errors
Test trigger manually

Pricing Considerations

Zapier integration uses your Zapier task quota. Each action (Create Request, Get Status) counts as one task. The workflow uses polling to wait for human responses before ending execution.

Next Steps

n8n Integration

Explore n8n for more advanced automation capabilities

Make Integration

Learn about Make.com with webhook triggers

API Reference

View complete API documentation

Community Templates

Browse Zapier templates shared by the community

Getting Started

Integration Guides

Core Concepts

Mobile App

Requests

Responses

Integrations

​Zapier Integration

​Why Use Zapier with HITL.sh?

7,000+ App Integrations

No-Code Automation

Multi-Step Workflows

Instant Setup

​Available Actions

​Create Request Action

​Supported Response Types

​Request Configuration

​Required Fields

​Optional Fields

​Status Codes

pending

completed

timeout

cancelled

​Example Workflows

​Content Approval from Google Forms

​Slack Message Moderation

​Customer Refund Workflow

​Using Paths for Conditional Logic

​Best Practices

Test Thoroughly

Use Filters

Error Handling

Monitor Usage

​Troubleshooting

​Pricing Considerations

​Next Steps

n8n Integration

Make Integration

API Reference

Community Templates

Zapier Integration

Why Use Zapier with HITL.sh?

Available Actions

Create Request Action

Supported Response Types

Request Configuration

Required Fields

Optional Fields

Status Codes

Example Workflows

Content Approval from Google Forms

Slack Message Moderation

Customer Refund Workflow

Using Paths for Conditional Logic

Best Practices

Troubleshooting

Pricing Considerations

Next Steps