Skip to main content
Webhooks let Agent Handler notify your systems when important events occur, and also consume events from third-party services. Agent Handler supports both outbound webhooks (events from Agent Handler to you) and inbound webhooks (events from third parties into Agent Handler, then forwarded to you).

​
Outbound webhooks

Outbound webhooks allow Agent Handler to send HTTP requests to your server when specific internal events occur. For example, you can receive a webhook every time a registered user is created or deleted.

​
Prerequisites

  • A server endpoint that can receive HTTP POST requests
    • For testing, we recommend using webhook.site or a similar tool.

​
Step 1: Navigate to Webhooks

  1. In Agent Handler, go to Settings.
  2. Open the Webhooks section.

​
Step 2: Configure your callback URL

  1. Click Add webhook (or edit an existing one).
  2. In Callback URL, enter the HTTPS endpoint on your server that will receive webhook events.
  3. Save your changes.
Your server should be prepared to:
  • Accept POST requests.
  • Parse the JSON payload.
  • Return an appropriate HTTP status code (for example, 200 OK on success).

​
Step 3: Subscribe to events

  1. In the same Webhooks configuration screen, find the Events section.
  2. Select the events you want to subscribe to. For example:
    • registered user created
    • registered user deleted
  3. Save your configuration.
Agent Handler will now send a POST request to your callback URL whenever one of the selected events occurs.

​
Step 4: Test your outbound webhook

To verify your configuration:
  1. In Agent Handler, create a test registered user.
  2. In your webhook receiver (for example, your server logs or webhook.site), confirm that a new request was received.
  3. Inspect the payload and verify:
    • The event type matches what you subscribed to.
    • The body contains the expected event data (for example, registered user identifiers and metadata).
Tip
For quick validation without deploying your own server, use webhook.site to generate a temporary callback URL and inspect requests in the browser.

​
Inbound webhooks (passthrough)

Inbound webhooks allow Agent Handler to receive events from third-party services (such as Slack) and then forward those events to your outbound webhook endpoint. Agent Handler handles the service-specific registration and verification flow, so you can focus on handling a unified event stream.
Important
Inbound webhooks are passthrough only. Every inbound webhook must be paired with an outbound webhook subscription to forward events to your server.

​
Prerequisites

Before configuring inbound webhooks, ensure you have:
  • A server endpoint to receive outbound webhooks
  • At least one outbound webhook configured and subscribed to “inbound webhook received” (described below).
  • Any connector-specific requirements. For Slack, you need:
    • A Slack app installed in your workspace.
    • Access to the app’s signing secret.

​
Step 1: Subscribe your outbound webhook to inbound events

  1. Go to Settings → Webhooks in Agent Handler.
  2. Edit the outbound webhook you want to use as the destination.
  3. In the Events list, enable “inbound webhook received” (or equivalent).
  4. Save your changes.
Now, whenever Agent Handler receives an inbound webhook from a third-party connector, it will send a corresponding event to this outbound webhook endpoint.

​
Step 2: Enable inbound webhooks for a connector

  1. In Agent Handler, navigate to the connector you want to configure (for example, Slack).
  2. If inbound webhooks are supported for that connector, you’ll see a Webhook section in its settings.
  3. Open the Webhook section to start configuration.

​
Step 3: Connector-specific setup (Slack example)

The exact setup varies by connector. This example walks through Slack.

​
1. Ensure the Slack app is installed

  1. Create or open your Slack app in the Slack developer dashboard.
  2. Install the app into your Slack workspace.

​
2. Locate your Slack signing secret

  1. In the Slack app’s dashboard, go to Basic Information → App Credentials.
  2. Copy the Signing Secret.

​
3. Configure inbound webhook in Agent Handler

  1. In Agent Handler, open your Slack connector.
  2. In the Webhook section, click Add inbound webhook.
  3. Paste the Slack signing secret into the appropriate field.
  4. Save the configuration.
After saving, the status in Agent Handler should show:
Awaiting confirmation (action needed)
Agent Handler has created a unique webhook URL, but Slack has not yet verified it.

​
Step 4: Verify the webhook URL in Slack

  1. In Agent Handler’s Slack connector settings, copy the webhook URL provided.
  2. In the Slack app’s dashboard, go to Event Subscriptions.
  3. Enable Event Subscriptions.
  4. Paste the Agent Handler webhook URL into the Request URL field.
  5. Slack will send a verification request to that URL:
    • Agent Handler will handle the challenge/verification flow.
    • If successful, Slack will show the URL as verified.
  6. In Subscribe to events, select the specific events you want Agent Handler to receive. For example:
    • channel_created
    • channel_joined
  7. Save your changes in Slack.

​
Step 5: Confirm active status in Agent Handler

  1. Return to the Slack connector settings page in Agent Handler.
  2. Refresh the page.
  3. Confirm that the inbound webhook status now shows as Active.
At this point, Slack events that you subscribed to will be delivered to Agent Handler, and then forwarded to your outbound webhook endpoint as “inbound webhook received” events.

​
Testing inbound webhooks

To verify that inbound webhooks are correctly configured end-to-end:
  1. Trigger an event in the third-party service
    • For Slack, you can:
      • Create a new channel.
      • Perform another action that emits one of the subscribed events.
  2. Check your outbound webhook endpoint
    • On your server (or webhook.site), look for a new webhook request from Agent Handler.
    • Confirm that:
      • The event type indicates an inbound webhook was received.
      • The payload contains the data from the third-party event.
        For example, when creating a Slack channel you may see:
        • channel_created
        • channel_joined
  3. Validate payload structure
    • Ensure your application can parse and handle the payload.
    • Optionally log samples in non-production environments to inform your event handling logic.

​
Next steps

Once you have webhooks configured:
  • Use outbound webhooks to keep your systems in sync with key Agent Handler events.
  • Use inbound webhooks (via supported connectors like Slack) to react to external events with your agents.
  • Combine webhooks with your Tool Packs and connectors to build rich, event-driven workflows for your agents.