The problem

n8n's human-in-the-loop options (Wait nodes, form triggers, Slack approvals) route to people already inside your account. When the workflow needs a stranger with a credential — a notary, a licensed reviewer, someone physically near the property — the workflow stops being no-code and starts being somebody's job.

The pattern

Two nodes, no custom code:

┌─────────────┐   ┌──────────────────────┐   ┌───────────────────────┐   ┌──────────────┐
│ (your flow) │──►│ HTTP Request         │──►│ Wait — On Webhook     │──►│ (your flow)  │
│             │   │ POST api.roji.ai     │   │ Call resumes when     │   │ deliverable  │
│             │   │ /v1/orders           │   │ order.delivered fires │   │ as JSON      │
└─────────────┘   └──────────────────────┘   └───────────────────────┘   └──────────────┘

(ordering tools land with the platform release)

1. HTTP Request node places the order — the service id, inputs from prior nodes, and the fee preview reference you accepted. The listing sets the price and the SLA, so there is nothing to bid or budget. Use a listing whose input template matches your data (doc-review/v1, field-photos/v1, verification-call/v1) and the deliverable schema is pre-built. Set the callback to your Wait node's webhook URL.
2. Wait node (On Webhook Call) resumes when ROJI delivers order.delivered. The payload is the deliverable itself: schema-validated JSON your downstream nodes map directly — no PDF parsing, no inbox scraping.
3. Optional: a second webhook path for order.question_asked lets a small branch answer typed questions from the business using data already in the workflow (most answers are lookups you already have).

Payment happens at order — the list price plus the platform fee, itemized in the fee preview before anything is charged, settling straight to the business. ROJI never holds the money. Spend caps are enforced platform-side, so a runaway loop can't drain anything.

What to expect

Turnaround by category: minutes for verification calls, hours for field capture, days for document review. You never have to guess which — the business publishes its SLA on the listing and your workflow can read it before it orders. If the business rejects the order or misses that SLA, the refund is automatic and full and your error branch fires with machine-readable detail — the workflow never hangs on silence. Full guarantees on the ordering page.

Design partners

The step you couldn't automate
is now a node.

We're onboarding n8n and automation teams now — bring one workflow with a human-shaped hole in it.

Get started