Webhooks

A webhook trigger gives an agent its own web address. When your system sends JSON data there, a new task starts with that data.

Some examples:

• A new order on your store starts an order-confirmation agent.
• A website form starts a lead qualifier.
• Your billing system flags an overdue invoice and starts a payment follow-up.

How they fit in

• A webhook is one of an agent's triggers, alongside schedules. You add both on the agent's Build tab, under Triggers.
• Only the agent's published version runs, and never while it is paused.
• The task it starts shows up in the tasks inbox like any other, with its steps and cost, and says which webhook started it. See Tasks and approvals.
• Approval rules still apply, so a webhook can't make an agent skip a step that needs your yes.

Set one up

Triggers, API keys and the run API covers creating a webhook, its secret, the request format, message templates, retries with Idempotency-Key, limits and errors.

Tip. To start tasks from incoming email, you don't need a webhook. See Answer customer emails.

Note. Dhanur AI also receives signed webhooks from its payment provider for its own billing. That endpoint is internal and not something you can use.