Webhooks let external services trigger your Autohive agents automatically. When a POST request is sent to a webhook URL, the associated agent runs with the request payload as its input.

Access Webhooks by clicking the Webhooks tab in your workspace header.

Creating a webhook

  1. Click Create webhook.
  2. Give the webhook a Name.
  3. Select the Agent that should run when the webhook is triggered.
  4. Click Create Webhook.

A unique webhook URL is generated automatically. Copy it using the copy button and provide it to the external service that will be sending requests.

Webhook URL

Each webhook has a unique URL in the format:

  https://app.autohive.com/{workspace}/hooks/{secret}

The secret embedded in the URL acts as the authentication token — no additional headers or signatures are required. You can copy the URL at any time from the webhook list or the edit form.

Testing a webhook

Before connecting an external service, you can test your webhook directly from Autohive:

  1. Open the three-dot menu on a webhook and select Test.
  2. Enter a JSON payload in the Test Payload field.
  3. Click Send Test.

The result shows whether the webhook triggered successfully and how long it took. You can click Send Again to re-run the test with the same or an updated payload.

Managing webhooks

The webhooks list shows all webhooks in your workspace with the following columns:

ColumnDescription
WebhookName, associated agent, and a badge showing any new failed executions
Created byThe member who created the webhook
URLThe webhook URL with a copy button
ActionsToggle on/off and access the options menu

Use the search bar to filter by name. Click the Webhook or Created by column headers to sort the list.

Enabling and disabling

Use the toggle switch on each webhook to turn it on or off. Disabled webhooks will not trigger when called.

Options menu

Click the three-dot menu on any webhook to:

  • Edit — update the name or associated agent
  • Test — send a test payload
  • Delete — permanently remove the webhook

Agents creating their own webhooks

As well as being created from the Webhooks tab, webhooks can now be created directly by your agents during a conversation. If you ask an agent to listen for an external event, it can set up its own inbound URL on the spot. This covers things like an incoming order, a form submission, or a status update from another system. There’s no need to visit the Webhooks tab.

While talking with an agent, it can:

  • Create a webhook — set up a new webhook that triggers itself, with its own name and description
  • List its webhooks — check which webhooks it has already created for itself
  • Edit its webhooks — change the name of a webhook it created, or pause and resume it
  • Cancel its webhooks — remove a webhook it created if it’s no longer needed

Webhooks an agent creates for itself appear alongside your own in the Webhooks list and behave the same way once created. They show up under your name in Created by, since the webhook runs on your behalf. They follow the same execution and failure-handling rules below. You can edit, toggle, or delete them yourself from the Webhooks tab at any time.

Plan access for agent-created webhooks

Creating a new webhook, renaming it, changing its description, and resuming a paused webhook all need the Webhooks capability on your plan. If your plan loses access to webhooks, an agent can still pause or cancel a webhook it already created -these two actions always stay available. If an agent tries to combine a rename with a pause in a single request, and the plan lacks webhook access, the whole request is declined and nothing changes. A follow-up request that only pauses the webhook will still succeed.

Execution history

Click any webhook in the list to open its execution history. Each execution shows:

  • Status — Succeeded, Failed, or Timed out
  • Date and time it was triggered
  • Error message if it failed

For successful executions, click View to open the agent conversation and see the output.

Handling failures

When an execution fails, a badge appears on the webhook showing the number of new issues. From the execution history you can:

  • Click Dismiss to acknowledge a failure and clear it from the badge count
  • Click Dismiss all issues to clear all unacknowledged failures at once

If the associated agent was deleted, an Assign another agent button appears. You can reassign the webhook without recreating it.