Zapier
Workflow automation
A Create Review Task action and an instant New Verdict trigger — no extra webhook app needed.
In plain English
LoopQuest is a place where a person quickly checks the work an AI or automation has done. Connecting Zapier means that whenever Zapier produces something that should be looked at by a human, it sends that item to LoopQuest. Someone on your team reviews it in a few seconds, and their decision is sent straight back to Zapier so the rest of your process can carry on, with a real person accountable for the call.
When you'd use it
A Zap watches a form or inbox and an AI step drafts an action. Send it to LoopQuest as a gate — the consequential step waits until a person approves — and a second Zap resumes the moment the verdict lands. Or run it as a monitor: the Zap carries on while reviews happen in the background for quality and audit.
The modules you get
Drag these into a Zapier scenario — each does one job so you can mix them to fit your flow.
Create Review Task
Sends your AI output to a human. Pick the game and the mode: gate blocks a downstream action until someone approves; monitor reviews in the background. Set a timeout + on-timeout fallback so nothing hangs.
New Verdict (trigger)
An instant trigger that fires the moment any review resolves — with the verdict, choice, reason, flags (escalated, timed_out) and your external_id. Zapier auto-subscribes when you turn the Zap on and unsubscribes when you turn it off.
What you'll need
- A free LoopQuest account. Sign up if you don't have one.
- A project and its API key — find it under Workspaces → your project → API keys. The key is how Zapier proves it's allowed to send you work.
- An account on Zapier itself, with the workflow or agent you want to add a human check to.
How to set it up
- 1Add the LoopQuest app to your Zap and connect it with your project API key.
- 2Add Create Review Task — choose a game, set mode to gate (to block) or monitor (to observe), and map your content. For a gate, set a timeout and on-timeout fallback.
- 3In a second Zap, add the New Verdict trigger, connect the same key, and turn the Zap on — Zapier subscribes it to your workspace's verdicts automatically.
- 4Add Paths/Filter after New Verdict: on approve, run the real action; on flag or timeout, route to a fallback. The external_id ties the verdict back to the item you sent.
Recipes: gate or monitor
Two ways to put a human in the loop with Zapier. A gate blocks until someone approves; a monitor reviews in the background without slowing anything down.
Gate — block until approved
A single Zapier run can't pause for an external callback, so the gate is split across two flows joined by the verdict webhook.
- 1Flow A: send the output to LoopQuest as a gate, then let the flow finish.
- 2Add a webhook trigger that listens for the verdict.
- 3Flow B: triggered by that webhook, it performs the action only when the verdict is an approval.
- 4Pass an external_id on the task so Flow B knows which item it belongs to.
Monitor — review without blocking
Monitor mode never holds Zapier up. The flow proceeds immediately and LoopQuest reviews a copy for quality.
- 1Send the output with a mode of "monitor" and don't wait on the result.
- 2Zapier carries straight on, nothing is blocked.
- 3Verdicts are logged and scored over time. Sample a fraction for QA, or review every item.
What happens after a review
The moment a reviewer decides, LoopQuest sends the result back to the web address you gave it (your callback_url). The message says what was decided, whether it was approved, flagged, which option was picked, or the corrected values, so your automation can act on it automatically.
For developers: each callback is signed with an X-LoopQuest-Signature HMAC header. Verify it before trusting the payload. Full details are in the API reference.
Pairs well with
The review games that best fit the kind of output Zapier tends to produce.