> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Honeycomb Webhook Setup Guide

> Configure Honeycomb to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/honeycomb#getting-started) on the Honeycomb connector page.

<section data-guide-section data-guide-scopes="">
  <h2>What StackOne provisions automatically</h2>

  <p>When you connect a Honeycomb account, StackOne creates a team-level webhook recipient named <strong>StackOne</strong> via the Honeycomb API, pointing at your connection's callback URL and carrying a shared secret. Honeycomb echoes that secret back in the `X-Honeycomb-Webhook-Token` header on every delivery. You do not need to create or copy any URL yourself. Removing the connection deletes the recipient — but Honeycomb refuses to delete a recipient that any Trigger or Burn Alert still references, so remove the <strong>StackOne</strong> recipient from those alerts first, otherwise the disconnect reports a conflict and the recipient is left in place.</p>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Attach the StackOne recipient to your alerts</h2>

  <p>Honeycomb only posts to a recipient that an alert explicitly references, and there is no API to attach a recipient to every alert at once. Repeat these steps for each Trigger, SLO Burn Alert and Anomaly Detection you want delivered to StackOne.</p>

  <Steps>
    <Step title="Attach to a Trigger">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Open the Trigger you want events from.</p>

        <ul>
          <li>Go to your environment and open <strong>Triggers</strong></li>
          <li>Select the trigger, then click <strong>Edit</strong></li>
          <li>Under <strong>Recipients</strong>, click <strong>Add Recipient</strong></li>
          <li>Choose <strong>Webhook</strong>, then select the <strong>StackOne</strong> recipient</li>
          <li>Click <strong>Save</strong></li>
        </ul>
      </div>
    </Step>

    <Step title="Attach to an SLO Burn Alert">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Burn alerts are configured on the SLO that owns them.</p>

        <ul>
          <li>Go to your environment and open <strong>SLOs</strong></li>
          <li>Select the SLO, then open its <strong>Burn Alerts</strong></li>
          <li>Edit an existing burn alert or create one</li>
          <li>Under <strong>Recipients</strong>, add the <strong>StackOne</strong> webhook recipient</li>
          <li>Click <strong>Save</strong></li>
        </ul>
      </div>
    </Step>

    <Step title="Attach to Anomaly Detection">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Anomaly Detection notifications are configured per monitored signal.</p>

        <ul>
          <li>Open <strong>Anomaly Detection</strong> in your environment</li>
          <li>Select the signal you want notifications for</li>
          <li>Add the <strong>StackOne</strong> webhook recipient to its notification settings</li>
          <li>Save the configuration.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.