n8n
Workflow automation
A Create Review Task action and a Verdict trigger for your n8n workflows.
In plain English
LoopQuest is a place where a person quickly checks the work an AI or automation has done. Connecting n8n means that whenever n8n 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 n8n so the rest of your process can carry on, with a real person accountable for the call.
When you'd use it
An n8n workflow classifies inbound tickets with an LLM. Before it auto-replies, route the draft through LoopQuest: send it as a gate so the workflow blocks until a person approves, or as a monitor to review quality in the background. The Verdict trigger resumes the flow the moment a human decides.
The modules you get
Drag these into a n8n 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 (Swiper, Sorter, Redact, Grounding…) and the mode: gate blocks a downstream step until approved; monitor reviews in the background. Optional timeout + on-timeout fallback.
LoopQuest Trigger
Fires when a review resolves, handing the verdict, choice, reason and your external_id into a second workflow — so you can branch on approve vs flag and build a blocking gate.
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 n8n proves it's allowed to send you work.
- An account on n8n itself, with the workflow or agent you want to add a human check to.
How to set it up
- 1In n8n: Settings → Community Nodes → Install, and enter n8n-nodes-loopquest.
- 2Add LoopQuest credentials with your project API key (the credential self-tests against /api/v1/me).
- 3Drop the Create Review Task node into your flow, pick a game and mode (gate or monitor), and map the output you want reviewed.
- 4Add the LoopQuest Trigger node to a second flow to receive the verdict and continue — approve → proceed, flag → fallback.
Recipes: gate or monitor
Two ways to put a human in the loop with n8n. A gate blocks until someone approves; a monitor reviews in the background without slowing anything down.
Gate — block until approved
n8n can pause a run and resume it when the verdict arrives, which makes it a clean blocking gate.
- 1In your n8n flow, send the output to LoopQuest with the mode set to "gate", plus a callback so it can be resumed.
- 2n8n 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 n8n 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.
- 2n8n 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 n8n tends to produce.