Pipedream
Workflow automation
A Create Review Task action and an instant New Verdict source for your workflows.
In plain English
LoopQuest is a place where a person quickly checks the work an AI or automation has done. Connecting Pipedream means that whenever Pipedream 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 Pipedream so the rest of your process can carry on, with a real person accountable for the call.
When you'd use it
A Pipedream workflow drafts a reply, scores a lead or proposes a refund with AI. Send it to LoopQuest as a gate — the consequential step waits until a person approves — and a second workflow resumes the moment the verdict lands. Or run it as a monitor: the workflow carries on while reviews happen in the background.
The modules you get
Drag these into a Pipedream scenario — each does one job so you can mix them to fit your flow.
Create Review Task
Sends your output to a human. Pick the game and the mode: gate blocks a downstream step until someone approves; monitor reviews in the background. Optional timeout + on-timeout fallback.
New Verdict (source)
A webhook trigger that emits the instant a review resolves — with the verdict, choice, reason, flags and your external_id. It subscribes on deploy and unsubscribes when removed.
Get Task Status
Look up a single review on demand — handy for a polling loop or a manual check.
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 Pipedream proves it's allowed to send you work.
- An account on Pipedream itself, with the workflow or agent you want to add a human check to.
How to set it up
- 1Add the LoopQuest app 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 workflow, add the New Verdict source — it registers itself with LoopQuest automatically on deploy.
- 4Branch on the verdict: approve → run the real action; 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 Pipedream. A gate blocks until someone approves; a monitor reviews in the background without slowing anything down.
Gate — block until approved
Pipedream can pause a run and resume it when the verdict arrives, which makes it a clean blocking gate.
- 1In your Pipedream flow, send the output to LoopQuest with the mode set to "gate", plus a callback so it can be resumed.
- 2Pipedream pauses at that step (a Wait node or resume URL) instead of carrying on.
- 3A reviewer approves or flags it; LoopQuest calls back and the run picks up exactly where it left off.
- 4Branch on the verdict, and set a timeout so a missing decision never blocks the flow forever.
Monitor — review without blocking
Monitor mode never holds Pipedream 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.
- 2Pipedream 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 Pipedream tends to produce.