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

# Honeycomb

> Send Honeycomb trigger alerts to Corelayer for investigation.

Connect Honeycomb triggers to Corelayer using a webhook recipient and a trigger payload template. This preset supports trigger alerts; SLO burn alerts are not supported.

## Prerequisites

You need permission to add webhooks in Corelayer and manage integrations and trigger recipients in your Honeycomb team.

## Setup

### 1. Create a source

In Corelayer, open **Webhooks** and click **Add Webhook**. Set **Webhook type** to **Honeycomb triggers**, enter a **Source name**, and click **Create Webhook**.

Copy the **Webhook URL**, **Webhook token**, and trigger payload template. The token is shown once, so store it before clicking **Done**.

### 2. Configure Honeycomb

In Honeycomb, open **Team Settings → Integrations**. Under **Trigger and SLO Recipients**, choose **Add Integration** and select **Webhook** as the provider.

Give the recipient a name, paste the Corelayer URL into **Webhook URL**, and paste the token into **Shared Secret**. Honeycomb sends this secret in the `X-Honeycomb-Webhook-Token` header. Use the token alone, without a `Bearer` prefix.

In the **Payload** tab, enable **Triggers** and paste this template, also provided by Corelayer:

```json theme={null}
{
  "alert_type": "trigger",
  "id": "{{ .ID }}",
  "instance_id": "{{ .Alert.InstanceID }}",
  "name": "{{ .Name }}",
  "description": "{{ .Description }}",
  "status": "{{ .Alert.Status }}",
  "summary": "{{ .Alert.Summary }}",
  "timestamp": "{{ .Alert.Timestamp }}",
  "url": "{{ .URL }}",
  "result_url": "{{ .Result.URL }}",
  "environment": "{{ .Environment }}",
  "datasets": {{ toJson .Datasets }},
  "operator": "{{ .Operator }}",
  "threshold": "{{ .Threshold }}",
  "query_time_range": "{{ .Query.TimeRange }}",
  "result_groups": {{ toJson .Result.Groups }},
  "groups_triggered": {{ toJson .Result.GroupsTriggered }},
  "is_test": "{{ .Alert.IsTest }}"
}
```

Click **Add** to save the recipient. Honeycomb's [webhook guide](https://docs.honeycomb.io/notify/webhooks) covers these settings.

### 3. Add the recipient to a trigger

Open a trigger in Honeycomb. Under **Recipients**, click **Add Recipient**, select the webhook, and click **Add**. Save the trigger. Repeat for each trigger you want to send to Corelayer.

When a trigger fires, look for the resulting investigation in Corelayer. Honeycomb test notifications are recorded without starting an investigation.

## How alerts are handled

`TRIGGERED` starts an investigation. `OK` records a resolution without closing the Corelayer issue. Other statuses and notifications marked `is_test` are recorded without investigation.

The payload includes the trigger name, summary, environment, datasets, threshold, and result groups. Corelayer also preserves links to the trigger and query result when available.

See [Manage sources](/webhooks/overview#manage-sources) to change or remove this source.

## Troubleshooting

* **No alert arrives:** Check that the webhook is a recipient on the trigger and that the trigger was saved.
* **`401` response:** Check the recipient's **Shared Secret** against the Corelayer token.
* **`400` response:** Check that the source uses **Honeycomb triggers** and that the **Triggers** payload matches the template. Keep `toJson` around the array fields; Honeycomb documents this in its [template variables reference](https://docs.honeycomb.io/notify/webhooks/variables).
* **No investigation starts:** Check the alert status and `is_test` value. A test or recovery notification does not start an investigation.

Need help? [Contact support](mailto:support@corelayer.com).


## Related topics

- [August 2026](/changelog/august-2026.md)
- [Custom alerts](/webhooks/custom.md)
- [Overview](/webhooks/overview.md)