# Honeycomb

> Send events and deploy markers to Honeycomb, run queries, and manage triggers. Start a workflow when a trigger or SLO burn alert fires, a marker is added, or a dataset stops receiving events.

App · 20 actions. Web page: https://docs.lodol.com/docs/integrations/honeycomb

## Actions

### Create marker

Mark a moment on Honeycomb's graphs, such as a deploy or an incident, so changes in the data can be traced to it.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Message (`message`, text, required): What happened, such as Deployed checkout v2.4.
- Type (`marker_type`, text): A group for similar markers, such as deploy; each type has its own color.
- Link (`url`, text): A page the marker's text opens, such as the build or release.
- Start (`start_time`, date and time): When it happened. Defaults to now.
- End (`end_time`, date and time): When it ended, to mark a span such as a 5-minute deploy.

**Outputs**

- `marker` (object): The marker

**Example output**

```json
{
  "marker": {
    "color": "#0298ec",
    "created_at": "2026-11-18T10:00:05Z",
    "end_time": 1763460300,
    "id": "d1c84ec0",
    "message": "Deployed checkout v2.4",
    "start_time": 1763460000,
    "type": "deploy",
    "updated_at": "2026-11-18T10:00:05Z",
    "url": "https://ci.example.com/builds/123"
  }
}
```

### Create trigger

Create a Honeycomb trigger that checks a calculation on a schedule and alerts when it crosses a threshold, such as more than 100 server errors in 15 minutes.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Name (`name`, text, required): Shown in Honeycomb and in each alert.
- Calculation (`calculation`, text): What to calculate. Defaults to a count of events. One of: `COUNT` (Count of events), `COUNT_DISTINCT` (Count of distinct values), `SUM`, `AVG` (Average), `MIN` (Minimum), `MAX` (Maximum), `P50` (Median (50th percentile)), `P75` (75th percentile), `P90` (90th percentile), `P95` (95th percentile), `P99` (99th percentile), `P999` (99.9th percentile). Default: `COUNT`.
- Field (`column`, text): The field to calculate on, such as duration_ms. Needed for every calculation except a count of events.
- Where (`filters`, list): Conditions events must meet, one per line, such as status_code >= 500, service.name = checkout or error exists.
- Match (`match`, text): Whether events must meet all the conditions or any one. One of: `all` (All conditions), `any` (Any condition). Default: `all`.
- Fire when the result is (`threshold_op`, text): Whether the trigger fires above or below the threshold. Defaults to above. One of: `>` (Above), `>=` (At or above), `<` (Below), `<=` (At or below). Default: `>`.
- Threshold (`threshold_value`, number, required): The number the result is compared with, such as 100.
- Check (`frequency_minutes`, text): How often Honeycomb checks. Defaults to every 15 minutes. One of: `1` (Every minute), `5` (Every 5 minutes), `10` (Every 10 minutes), `15` (Every 15 minutes), `30` (Every 30 minutes), `60` (Every hour), `120` (Every 2 hours), `360` (Every 6 hours), `720` (Every 12 hours), `1440` (Every day). Default: `15`.
- Look back over (`lookback_minutes`, text): How much time each check covers: from the time between checks to 4 times it. Defaults to the time between checks. One of: `1` (1 minute), `5` (5 minutes), `10` (10 minutes), `15` (15 minutes), `30` (30 minutes), `60` (1 hour), `120` (2 hours), `240` (4 hours), `360` (6 hours), `720` (12 hours), `1440` (24 hours).
- Alert (`alert_on`, text): Alert once when the threshold is crossed (default), or at every check. One of: `on_change` (Once, when it crosses the threshold), `on_true` (At every check while it is over the threshold). Default: `on_change`.
- Notify (`recipients`, list): Who Honeycomb alerts: the email addresses, Slack channels and others set up under Team Settings > Integrations.
- Description (`description`, text): Shown on the trigger's page, such as a runbook link.
- Turned off (`disabled`, true/false): Turn the trigger off, so it isn't checked and sends no alerts.

**Outputs**

- `trigger` (object): The trigger

**Example output**

```json
{
  "trigger": {
    "alert_type": "on_change",
    "created_at": "2026-11-01T09:00:00Z",
    "dataset_slug": "checkout",
    "description": "More than 100 server errors in 15 minutes",
    "disabled": false,
    "frequency": 900,
    "id": "fS4WfA82",
    "name": "Checkout errors",
    "query": {
      "calculations": [
        {
          "op": "COUNT"
        }
      ],
      "filters": [
        {
          "column": "status_code",
          "op": ">=",
          "value": 500
        }
      ],
      "time_range": 900
    },
    "query_id": "dSlAHrWyBu",
    "recipients": [
      {
        "id": "yUheCUmgZ8q",
        "target": "oncall@example.com",
        "type": "email"
      }
    ],
    "tags": [
      {
        "key": "team",
        "value": "payments"
      }
    ],
    "threshold": {
      "exceeded_limit": 1,
      "op": ">",
      "value": 100
    },
    "triggered": false,
    "updated_at": "2026-11-01T09:00:00Z"
  }
}
```

### Delete marker

Delete a marker from a dataset.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Marker (`marker_id`, text, required): The marker. Pick one, or give its ID from an earlier step.

**Outputs**

- `deleted` (true/false): Always true once done
- `marker_id` (text): The marker deleted

**Example output**

```json
{
  "deleted": true,
  "marker_id": "d1c84ec0"
}
```

### Delete trigger

Delete a Honeycomb trigger, so it no longer checks or alerts.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Trigger (`trigger_id`, text, required): The Honeycomb trigger. Pick one, or give its ID from an earlier step.

**Outputs**

- `deleted` (true/false): Always true once done
- `trigger_id` (text): The trigger deleted

**Example output**

```json
{
  "deleted": true,
  "trigger_id": "fS4WfA82"
}
```

### Get dataset

Get one dataset: its description, how many fields it has and when it last received an event.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one, or give its slug from an earlier step.

**Outputs**

- `dataset` (object): The dataset

**Example output**

```json
{
  "dataset": {
    "created_at": "2026-01-12T09:00:00Z",
    "description": "The checkout service",
    "expand_json_depth": 0,
    "last_written_at": "2026-11-18T10:04:00Z",
    "name": "checkout",
    "regular_columns_count": 42,
    "settings": {
      "delete_protected": false
    },
    "slug": "checkout"
  }
}
```

### Get SLO

Get one SLO, optionally with its status, error budget left and compliance (Honeycomb Enterprise).

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- SLO (`slo_id`, text, required): The SLO. Pick one, or give its ID from an earlier step.
- Include status and budget (`include_report`, true/false): Also return its status, error budget left, compliance and burn rate. Needs Honeycomb Enterprise.

**Outputs**

- `slo` (object): The SLO

**Example output**

```json
{
  "slo": {
    "budget_remaining": 48.2,
    "burn_rate": 0.8,
    "compliance": 99.95,
    "created_at": "2026-02-01T09:00:00Z",
    "dataset_slugs": [
      "checkout"
    ],
    "description": "99.9% of checkouts succeed",
    "id": "bZ1aRHAUsjG",
    "name": "Checkout succeeds",
    "reset_at": "2026-06-01T00:00:00Z",
    "sli": {
      "alias": "checkout_ok"
    },
    "status": "normal",
    "tags": [],
    "target_per_million": 999000,
    "time_period_days": 30,
    "updated_at": "2026-02-01T09:00:00Z"
  }
}
```

### Get trigger

Get one Honeycomb trigger: its query, threshold, schedule, who it notifies and whether it is firing.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Trigger (`trigger_id`, text, required): The Honeycomb trigger. Pick one, or give its ID from an earlier step.

**Outputs**

- `trigger` (object): The trigger

**Example output**

```json
{
  "trigger": {
    "alert_type": "on_change",
    "created_at": "2026-11-01T09:00:00Z",
    "dataset_slug": "checkout",
    "description": "More than 100 server errors in 15 minutes",
    "disabled": false,
    "frequency": 900,
    "id": "fS4WfA82",
    "name": "Checkout errors",
    "query": {
      "calculations": [
        {
          "op": "COUNT"
        }
      ],
      "filters": [
        {
          "column": "status_code",
          "op": ">=",
          "value": 500
        }
      ],
      "time_range": 900
    },
    "query_id": "dSlAHrWyBu",
    "recipients": [
      {
        "id": "yUheCUmgZ8q",
        "target": "oncall@example.com",
        "type": "email"
      }
    ],
    "tags": [
      {
        "key": "team",
        "value": "payments"
      }
    ],
    "threshold": {
      "exceeded_limit": 1,
      "op": ">",
      "value": 100
    },
    "triggered": false,
    "updated_at": "2026-11-01T09:00:00Z"
  }
}
```

### List boards

List the boards in your environment, with a link to each.

**Inputs**: None.

**Outputs**

- `boards` (list): The boards
- `count` (number): How many

**Example output**

```json
{
  "boards": [
    {
      "description": "Errors and latency for checkout",
      "id": "2NeeaE9bBLd",
      "links": {
        "board_url": "https://ui.honeycomb.io/acme/environments/prod/board/2NeeaE9bBLd"
      },
      "name": "Checkout health",
      "panels": [],
      "tags": [],
      "type": "flexible"
    }
  ],
  "count": 1
}
```

### List burn alerts

List an SLO's burn alerts, which warn when its error budget runs down, and whether each is firing.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- SLO (`slo_id`, text, required): The SLO. Pick one, or give its ID from an earlier step.

**Outputs**

- `burn_alerts` (list): The burn alerts
- `count` (number): How many

**Example output**

```json
{
  "burn_alerts": [
    {
      "alert_type": "exhaustion_time",
      "created_at": "2026-02-01T09:00:00Z",
      "description": "Use the checkout runbook",
      "id": "fS7vfB81Wcy",
      "slo": {
        "id": "bZ1aRHAUsjG"
      },
      "triggered": false,
      "updated_at": "2026-02-01T09:00:00Z"
    }
  ],
  "count": 1
}
```

### List datasets

List the datasets in your environment, with when each last received an event.

**Inputs**: None.

**Outputs**

- `count` (number): How many
- `datasets` (list): The datasets

**Example output**

```json
{
  "count": 1,
  "datasets": [
    {
      "created_at": "2026-01-12T09:00:00Z",
      "description": "The checkout service",
      "expand_json_depth": 0,
      "last_written_at": "2026-11-18T10:04:00Z",
      "name": "checkout",
      "regular_columns_count": 42,
      "settings": {
        "delete_protected": false
      },
      "slug": "checkout"
    }
  ]
}
```

### List fields

List the fields in a dataset's events, with each one's type and when an event last carried it.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.

**Outputs**

- `columns` (list): The fields
- `count` (number): How many

**Example output**

```json
{
  "columns": [
    {
      "created_at": "2026-01-12T09:00:00Z",
      "description": "",
      "hidden": false,
      "id": "yUheCUmgZ8p",
      "key_name": "duration_ms",
      "last_written": "2026-11-18T10:04:00Z",
      "type": "float",
      "updated_at": "2026-01-12T09:00:00Z"
    }
  ],
  "count": 1
}
```

### List markers

List a dataset's markers, newest first.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Type (`marker_type`, text): Only markers of this type, such as deploy.
- At most (`limit`, number): How many markers to return. Defaults to 100. From 1 to 1000.

**Outputs**

- `count` (number): How many
- `markers` (list): The markers, newest first

**Example output**

```json
{
  "count": 1,
  "markers": [
    {
      "color": "#0298ec",
      "created_at": "2026-11-18T10:00:05Z",
      "end_time": 1763460300,
      "id": "d1c84ec0",
      "message": "Deployed checkout v2.4",
      "start_time": 1763460000,
      "type": "deploy",
      "updated_at": "2026-11-18T10:00:05Z",
      "url": "https://ci.example.com/builds/123"
    }
  ]
}
```

### List recipients

List where Honeycomb can send alerts: email addresses, Slack channels, PagerDuty and webhooks. Secrets are hidden.

**Inputs**: None.

**Outputs**

- `count` (number): How many
- `recipients` (list): The recipients

**Example output**

```json
{
  "count": 1,
  "recipients": [
    {
      "created_at": "2026-01-12T09:00:00Z",
      "details": {
        "email_address": "oncall@example.com"
      },
      "id": "yUheCUmgZ8q",
      "type": "email",
      "updated_at": "2026-01-12T09:00:00Z"
    }
  ]
}
```

### List SLOs

List the service level objectives (SLOs) on a dataset. Needs Honeycomb Pro or Enterprise.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.

**Outputs**

- `count` (number): How many
- `slos` (list): The SLOs

**Example output**

```json
{
  "count": 1,
  "slos": [
    {
      "budget_remaining": 48.2,
      "burn_rate": 0.8,
      "compliance": 99.95,
      "created_at": "2026-02-01T09:00:00Z",
      "dataset_slugs": [
        "checkout"
      ],
      "description": "99.9% of checkouts succeed",
      "id": "bZ1aRHAUsjG",
      "name": "Checkout succeeds",
      "reset_at": "2026-06-01T00:00:00Z",
      "sli": {
        "alias": "checkout_ok"
      },
      "status": "normal",
      "tags": [],
      "target_per_million": 999000,
      "time_period_days": 30,
      "updated_at": "2026-02-01T09:00:00Z"
    }
  ]
}
```

### List triggers

List the Honeycomb triggers (alerts) on a dataset, and whether each is firing.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Status (`status`, text): Only triggers that are firing, not firing, or turned off. One of: `firing` (Firing now), `ok` (Not firing), `disabled` (Turned off).

**Outputs**

- `count` (number): How many
- `triggers` (list): The triggers

**Example output**

```json
{
  "count": 1,
  "triggers": [
    {
      "alert_type": "on_change",
      "created_at": "2026-11-01T09:00:00Z",
      "dataset_slug": "checkout",
      "description": "More than 100 server errors in 15 minutes",
      "disabled": false,
      "frequency": 900,
      "id": "fS4WfA82",
      "name": "Checkout errors",
      "query": {
        "calculations": [
          {
            "op": "COUNT"
          }
        ],
        "filters": [
          {
            "column": "status_code",
            "op": ">=",
            "value": 500
          }
        ],
        "time_range": 900
      },
      "query_id": "dSlAHrWyBu",
      "recipients": [
        {
          "id": "yUheCUmgZ8q",
          "target": "oncall@example.com",
          "type": "email"
        }
      ],
      "tags": [
        {
          "key": "team",
          "value": "payments"
        }
      ],
      "threshold": {
        "exceeded_limit": 1,
        "op": ">",
        "value": 100
      },
      "triggered": false,
      "updated_at": "2026-11-01T09:00:00Z"
    }
  ]
}
```

### Run query

Count or calculate over a dataset's events, such as the 99th percentile of duration_ms by service in the last hour, and get the results. Needs Honeycomb Enterprise.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Calculation (`calculation`, text): What to calculate. Defaults to a count of events. One of: `COUNT` (Count of events), `COUNT_DISTINCT` (Count of distinct values), `SUM`, `AVG` (Average), `MIN` (Minimum), `MAX` (Maximum), `P50` (Median (50th percentile)), `P75` (75th percentile), `P90` (90th percentile), `P95` (95th percentile), `P99` (99th percentile), `P999` (99.9th percentile). Default: `COUNT`.
- Field (`column`, text): The field to calculate on, such as duration_ms. Needed for every calculation except a count of events.
- Where (`filters`, list): Conditions events must meet, one per line, such as status_code >= 500, service.name = checkout or error exists.
- Match (`match`, text): Whether events must meet all the conditions or any one. One of: `all` (All conditions), `any` (Any condition). Default: `all`.
- Group by (`group_by`, list): Fields to split the results by, such as service.name.
- Time range (`time_range`, text): How far back to look. Defaults to the last 2 hours. One of: `600` (Last 10 minutes), `1800` (Last 30 minutes), `3600` (Last hour), `7200` (Last 2 hours), `21600` (Last 6 hours), `86400` (Last 24 hours), `604800` (Last 7 days). Default: `7200`.
- From (`start_time`, date and time): The start of a fixed time range, instead of Time range. Fill in To as well; at most 7 days, within the past 7 days.
- To (`end_time`, date and time): The end of a fixed time range.
- At most (`limit`, number): How many result rows (groups) to return. Defaults to 100. From 1 to 1000.

**Outputs**

- `count` (number): How many
- `graph_image_url` (text): A picture of the graph
- `query_id` (text): The query's ID
- `query_result_id` (text): The ID of this run of the query
- `query_url` (text): The results in Honeycomb
- `results` (list): One row per group: the group-by fields and the calculation, such as COUNT or P99(duration_ms)

**Example output**

```json
{
  "count": 1,
  "graph_image_url": "https://ui.honeycomb.io/acme/datasets/checkout/result/dfg456/snapshot",
  "query_id": "abc3419d",
  "query_result_id": "dfg456",
  "query_url": "https://ui.honeycomb.io/acme/datasets/checkout/result/dfg456",
  "results": [
    {
      "P99(duration_ms)": 857.03,
      "service.name": "checkout"
    }
  ]
}
```

### Send event

Send one event to a dataset, such as a job that finished with its duration. A new dataset name creates the dataset.

**Inputs**

- Dataset (`dataset`, text, required): The dataset to send to. Pick one, or type a new name to create it.
- Fields (`fields`, object, required): The event's fields and values, such as job: nightly-import and duration_ms: 5400.
- Time (`event_time`, date and time): When it happened. Defaults to now.
- Sample rate (`sample_rate`, number): If you send 1 in every N events, N, so Honeycomb counts this one N times. Defaults to 1. At least 1.

**Outputs**

- `dataset` (text): The dataset they went to
- `sent` (number): How many events Honeycomb stored

**Example output**

```json
{
  "dataset": "checkout",
  "sent": 1
}
```

### Send events

Send a list of events to a dataset in one go, such as rows from an earlier step. Fails, naming each event, if Honeycomb refuses any.

**Inputs**

- Dataset (`dataset`, text, required): The dataset to send to. Pick one, or type a new name to create it.
- Events (`events`, list, required): A list of events, each a set of fields and values. An item may also give data, time and samplerate as Honeycomb does.

**Outputs**

- `dataset` (text): The dataset they went to
- `sent` (number): How many events Honeycomb stored

**Example output**

```json
{
  "dataset": "checkout",
  "sent": 25
}
```

### Update marker

Change a marker's message, type, link or times, such as adding the end of a deploy. Fields left blank keep what the marker has.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Marker (`marker_id`, text, required): The marker. Pick one, or give its ID from an earlier step.
- Message (`message`, text): What happened, such as Deployed checkout v2.4. Leave blank to keep it.
- Type (`marker_type`, text): A group for similar markers, such as deploy; each type has its own color. Leave blank to keep it.
- Link (`url`, text): A page the marker's text opens, such as the build or release. Leave blank to keep it.
- Start (`start_time`, date and time): When it happened. Leave blank to keep it.
- End (`end_time`, date and time): When it ended, to mark a span such as a 5-minute deploy. Leave blank to keep it.

**Outputs**

- `marker` (object): The marker

**Example output**

```json
{
  "marker": {
    "color": "#0298ec",
    "created_at": "2026-11-18T10:00:05Z",
    "end_time": 1763460300,
    "id": "d1c84ec0",
    "message": "Deployed checkout v2.4",
    "start_time": 1763460000,
    "type": "deploy",
    "updated_at": "2026-11-18T10:00:05Z",
    "url": "https://ci.example.com/builds/123"
  }
}
```

### Update trigger

Change a Honeycomb trigger's name, threshold, schedule or who it notifies, or turn it off or on. Fields left blank stay as they are.

**Inputs**

- Dataset (`dataset`, text, required): The dataset. Pick one (or every dataset), or give its slug from an earlier step.
- Trigger (`trigger_id`, text, required): The Honeycomb trigger. Pick one, or give its ID from an earlier step.
- Name (`name`, text): A new name. Leave blank to keep it.
- Description (`description`, text): A new description. Leave blank to keep it.
- Fire when the result is (`threshold_op`, text): Above or below. Leave blank to keep it. One of: `>` (Above), `>=` (At or above), `<` (Below), `<=` (At or below).
- Threshold (`threshold_value`, number): A new threshold. Leave blank to keep it.
- Check (`frequency_minutes`, text): How often to check. Leave blank to keep it; it must suit how far back the trigger looks. One of: `1` (Every minute), `5` (Every 5 minutes), `10` (Every 10 minutes), `15` (Every 15 minutes), `30` (Every 30 minutes), `60` (Every hour), `120` (Every 2 hours), `360` (Every 6 hours), `720` (Every 12 hours), `1440` (Every day).
- Alert (`alert_on`, text): Once, or at every check. Leave blank to keep it. One of: `on_change` (Once, when it crosses the threshold), `on_true` (At every check while it is over the threshold).
- Notify (`recipients`, list): Replaces who Honeycomb alerts. Leave blank to keep them.
- Turned off (`disabled`, true/false): Turn the trigger off (true) or on (false). Leave blank to keep it.

**Outputs**

- `trigger` (object): The trigger

**Example output**

```json
{
  "trigger": {
    "alert_type": "on_change",
    "created_at": "2026-11-01T09:00:00Z",
    "dataset_slug": "checkout",
    "description": "More than 100 server errors in 15 minutes",
    "disabled": false,
    "frequency": 900,
    "id": "fS4WfA82",
    "name": "Checkout errors",
    "query": {
      "calculations": [
        {
          "op": "COUNT"
        }
      ],
      "filters": [
        {
          "column": "status_code",
          "op": ">=",
          "value": 500
        }
      ],
      "time_range": 900
    },
    "query_id": "dSlAHrWyBu",
    "recipients": [
      {
        "id": "yUheCUmgZ8q",
        "target": "oncall@example.com",
        "type": "email"
      }
    ],
    "tags": [
      {
        "key": "team",
        "value": "payments"
      }
    ],
    "threshold": {
      "exceeded_limit": 1,
      "op": ">",
      "value": 100
    },
    "triggered": false,
    "updated_at": "2026-11-01T09:00:00Z"
  }
}
```
