gotoHuman vs Inngest

gotoHuman

Built for agent review, with TypeScript and Python SDKs, a 3-tool MCP server, an n8n node and a Make app. No status page, published rate limits or documented error responses.

Inngest

Waits are durable and cost nothing while suspended, with runs up to 30 days on Free and 366 on Business. No reviewer inbox, Slack app or email, so the human side is your code.

gotoHuman

1. Call get-form-schema before request-human-review-with-form, since the field data must match the review type
2. Send agentId on every API request, because the API reference marks it required even though the JS SDK doesn't
3. Pass a webhookUrl per request when the review type has no default, or the answer has nowhere to go
4. Deduplicate webhook calls on the Idempotency-Key header, since delivery is at least once
5. Set your own deadline on the agent side and treat silence as a rejection

Inngest

1. Use step.waitForSignal() when one run waits for one answer, and waitForEvent only when one answer resumes many runs
2. Register the wait before you send the approval request, or check the external state first, since early events are missed
3. Use a unique approval ID per tool call and match on it, so parallel approvals resolve independently
4. Treat null or undefined as a timeout and decide on purpose whether that rejects, approves or escalates
5. Set an event id when sending the answer, so a retried send is dropped within 24 hours