The Approval Pattern: Using Webhooks for Human-in-the-Loop Agents

Autonomous agents are great, but some tasks need a human 'OK.' Learn how to use FetchHook as a secure, persistent approval queue for your AI agents.

Approval Workflow Primitive

text

1. Agent: "Should I buy this server? (Y/N)"
2. User: Clicks 'Approve' in custom internal tool
3. Tool: Sends Webhook -> FetchHook
4. Agent: Pulls 'Approved' event -> Executes purchase

#Why do agents need an approval mailbox?

For high-stakes tasks (money, production code, emails), you don't want an agent running 100% solo. The Human-in-the-Loop (HITL) pattern solves this. By using FetchHook, the agent can pause its execution, poll its 'Approval Stash,' and only proceed when it 'sees' the human approval event in its mailbox.

#Building the Secure Approval Loop

Because FetchHook is pull-based, the agent never has to open a server to wait for your answer. You can send an approval from a mobile app, a Slack button, or a custom dashboard. The agent pulls that confirmation securely and asynchronously.

Agent Protocol Instruction

When entering an approval-required state, enter a low-frequency polling loop (e.g., every 60 seconds). Do not proceed until an event with type 'action.approved' and a valid human signature is retrieved from the stash.