Zapier integration
Native integration preview
The maker-owned HIC Zapier integration is private and not publicly listed. The existing 1.0.1 version uses a project API key. A new 2.0.0 OAuth candidate adds HIC account sign-in, a saved account connection, permitted project/inbox dropdowns and typed fields from the chosen inbox form. Existing 1.x connections stay pinned to their API-key version.
After OAuth deployment and private acceptance, start a Zap with your source app's trigger. Add HIC as an action, connect your HIC account, select a project and inbox, and map title/content plus a stable Source Item ID. Use the inbox's typed form fields or advanced custom JSON. Static values and mappings from earlier steps are supported.
- Create Decision Request returns immediately.
- Create Decision Request and Wait supplies its callback URL automatically and pauses the same Zap for up to 30 days. It verifies the exact review through HIC's authenticated API before returning committed values.
- Get Decision retrieves status and committed edited output using the same project.
- Recall Decision Request cancels a pending request before a human decision commits.
- Decision Resolved is a separate polling trigger, limited to the latest 100 decisions for that connection/project/inbox. Use the waiting action for continuation of the same Zap.
Approve and reject are both human outcomes. Route protected actions only when outcome is approved, use output/final_values, and provide effect_key for downstream idempotency. An undo-window proposal cannot continue. HIC account permissions and consent apply even to mapped IDs. Existing Free/Lite/Pro limits and billing remain unchanged.
Native OAuth is a release candidate pending deployment and hosted sign-in/refresh/wait acceptance. No customer must enter a developer client ID. The maker configures the registered OAuth client once. Logo and category settings are independent of source uploads. The Webhooks recipe below remains available during preview; guided templates and a public listing are separate deliverables.
Webhooks alternative
Check that your Zapier plan supports Webhooks steps.
Submit a review
Use Webhooks by Zapier → Custom Request.
Method:
POST
URL:
https://humanincircuit.com/v2/reviews
Headers:
Authorization: Bearer <HIC_PROJECT_API_KEY>
Content-Type: application/json
Idempotency-Key: <stable-zap-item-id>
Body:
{
"title": "Approve Zapier output",
"inbox_key": "<YOUR_INBOX_KEY>",
"external_id": "<STABLE_SOURCE_ITEM_ID>",
"summary": "A Zap generated something that needs review.",
"initial_values": {
"message": "Generated text..."
},
"fields": [
{
"key": "message",
"label": "Message",
"type": "textarea",
"required": true
}
],
"callback": {
"url": "https://hooks.zapier.com/hooks/catch/..."
}
}
Continue after review
Use Webhooks by Zapier → Catch Hook as the continuation trigger.
Allowlist this callback hostname on the Human In Circuit API key:
hooks.zapier.com
Use the General project and General reviews inbox created on signup. Copy the inbox key and create a project API key in Settings → Organization admin → Projects. Configure the inbox's approval behavior there; do not create another project or require a legacy Automation/workflow record.
Build the continuation Zap first so you can paste its Catch Hook URL into the request Zap. In the continuation, correlate external_id with the source item, filter on outcome, and use output / final_values only on the approved branch. Rejects must not run the protected action. Deduplicate event_id before downstream side effects: callbacks may be retried.
Before a production action, verify the callback signature using callback authentication, or retrieve the review through the authenticated GET /v2/reviews/{review_id} endpoint and verify its final status and expected external ID. Do not treat an unverified incoming webhook as proof of approval.
Reuse this setup
There is no published HIC Zapier template link yet. After your two-Zap test passes, create guided templates from the request and continuation Zaps, leaving API key, inbox key, Catch Hook URL and connected accounts editable. Add those verified links to Workflow templates.
Do not create a new legacy shared Zap template: Zapier is retiring that sharing system. See Zapier's current guidance.