Human in the Loop

Most automation arguments are really one argument: people do not object to the agent doing the work, they object to it acting without asking.

This is the smallest thing that resolves that. A pipeline posts a proposed action and a set of choices. The service stores it, returns a review URL, and waits. A person opens the link, picks an option, and the service fires a webhook back so the pipeline continues down the branch they chose. If a caller marks an action as safe, it can skip review entirely and call the webhook immediately.

That is the whole product. A Worker, a KV namespace, and a React review page.

It is not a demo. It is the approval step inside the n8n sales pipelines I built at inBeat: leads get enriched and scored, then a Slack message carries a review link, and a rep’s choice drives what happens next in the CRM and the calendar.

The useful lesson was about scope. Every version of this that tried to also be a workflow tool, a queue, or a notification system got worse. Doing one thing means it drops into any pipeline that can make an HTTP request.