> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/honeybadger.md).

# Honeybadger

Track application errors, resolve faults, report errors, and record deployments.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector   | Authentication      |
| ----------- | ------------------- |
| Honeybadger | Personal Auth Token |

#### Honeybadger

Connect Honeybadger with a personal auth token.

**Set up in Honeybadger**

1. Prepare the Honeybadger account or service that the workflow will access. Grant access to the required resources and operations.
2. **Personal Auth Token:** Create a personal auth token on the Honeybadger account settings page.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Honeybadger**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field       | Required                 | What to enter                                                                                                                          |
| ------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| Personal Auth Token | Yes                      | Create a personal auth token on the Honeybadger account settings page. [Provider instructions](https://app.honeybadger.io/users/edit). |
| Data Region         | Optional / as applicable | The region hosting this Honeybadger account. EU accounts live at eu-app.honeybadger.io; use 'us' otherwise.                            |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Honeybadger** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### List Projects

List the Honeybadger projects you can access, with their error counts.

**Inputs**

| Field                 | Type    | Required | Description                                                                                                   |
| --------------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------- |
| Show advanced options | boolean | No       | Show the page size cap and page cursor. Default: false.                                                       |
| Max Projects          | integer | No       | Stop after at least this many projects. Results arrive in whole pages. Minimum: 1. Maximum: 250. Default: 50. |
| Page Cursor           | string  | No       | Continue from where an earlier run stopped.                                                                   |

**Outputs**

| Field       | Type          | Description                                                                                                                                                      |
| ----------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Projects    | object\_array | Projects with id, name, active flag, environments, fault\_count, unresolved\_fault\_count, created\_at, last\_notice\_at. The project API key is never included. |
| Next Cursor | string        | Pass to Page Cursor to get more projects.                                                                                                                        |

#### List Faults

Find errors (faults) in a Honeybadger project, filtered by status, environment, time, or search text.

**Inputs**

| Field                 | Type             | Required | Description                                                                                                            |
| --------------------- | ---------------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
| Project               | select (integer) | Yes      | The Honeybadger project to search. Options load from the selected connection.                                          |
| Status                | select (string)  | No       | Which faults to include. Available values: Unresolved, Resolved, Ignored, All. Default: unresolved.                    |
| Search                | string           | No       | Words to look for, or Honeybadger search filters such as class:"NoMethodError".                                        |
| Environment           | string           | No       | Only show faults from this environment.                                                                                |
| Show advanced options | boolean          | No       | Show sort order, time filter, page size cap, and page cursor. Default: false.                                          |
| Sort By               | select (string)  | No       | Show the most recent or the most frequent faults first. Available values: Most Recent, Most Frequent. Default: recent. |
| Occurred After        | datetime         | No       | Only include faults that happened after this time.                                                                     |
| Max Faults            | integer          | No       | Stop after at least this many faults. Pages hold up to 25 faults. Minimum: 1. Maximum: 100. Default: 25.               |
| Page Cursor           | string           | No       | Continue from where an earlier run stopped.                                                                            |

**Outputs**

| Field       | Type          | Description                                                                                                                                                |
| ----------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Faults      | object\_array | Faults with id, klass, message, environment, component, action, resolved, ignored, notices\_count, created\_at, last\_notice\_at, tags, url, and assignee. |
| Next Cursor | string        | Pass to Page Cursor to get more faults.                                                                                                                    |

#### Resolve Fault

Mark a Honeybadger error as resolved.

**Inputs**

| Field   | Type             | Required | Description                                                                                 |
| ------- | ---------------- | -------- | ------------------------------------------------------------------------------------------- |
| Project | select (integer) | Yes      | The Honeybadger project that contains the fault. Options load from the selected connection. |
| Fault   | select (integer) | Yes      | The error to resolve. Options load from the selected connection.                            |

**Outputs**

| Field      | Type    | Description                          |
| ---------- | ------- | ------------------------------------ |
| Project ID | integer | The project id.                      |
| Fault ID   | integer | The resolved fault id.               |
| Resolved   | boolean | True when the fault is now resolved. |

#### Report Error

Send an error to a Honeybadger project so it is tracked and alerts your team.

**Inputs**

| Field                 | Type             | Required | Description                                                                                      |
| --------------------- | ---------------- | -------- | ------------------------------------------------------------------------------------------------ |
| Project               | select (integer) | Yes      | The Honeybadger project that receives the error. Options load from the selected connection.      |
| Error Type            | string           | Yes      | A short name for the kind of error. Errors with the same type and location are grouped together. |
| Message               | textarea         | Yes      | What went wrong.                                                                                 |
| Environment           | string           | No       | The environment where the error happened. Default: production.                                   |
| Tags                  | string           | No       | Comma-separated tags to help filter errors later.                                                |
| Show advanced options | boolean          | No       | Show grouping key, component, and page URL. Default: false.                                      |
| Grouping Key          | string           | No       | Errors with the same grouping key are always grouped into one fault.                             |
| Component             | string           | No       | The part of your system where the error happened.                                                |
| Page URL              | string           | No       | The web page or endpoint related to the error.                                                   |

**Outputs**

| Field      | Type   | Description                     |
| ---------- | ------ | ------------------------------- |
| Notice ID  | string | The id of the reported notice.  |
| Notice URL | string | Open the notice in Honeybadger. |

#### Create Deployment

Record a deployment in Honeybadger so errors can be tied to a release. If the project resolves errors on deploy, this also resolves the open errors in the deployed environment.

**Inputs**

| Field                 | Type             | Required | Description                                                                                                                                                                |
| --------------------- | ---------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project               | select (integer) | Yes      | The Honeybadger project that was deployed. Options load from the selected connection.                                                                                      |
| Environment           | string           | No       | The environment you deployed to. Blank means production. If the project resolves errors on deploy, this resolves the open errors in this environment. Default: production. |
| Revision              | string           | No       | The commit, tag, or version you deployed.                                                                                                                                  |
| Show advanced options | boolean          | No       | Show repository and deployed-by fields. Default: false.                                                                                                                    |
| Repository URL        | string           | No       | The HTTPS URL of the source repository.                                                                                                                                    |
| Deployed By           | string           | No       | The person or system that deployed.                                                                                                                                        |

**Outputs**

| Field       | Type    | Description               |
| ----------- | ------- | ------------------------- |
| Project ID  | integer | The project id.           |
| Environment | string  | The recorded environment. |
| Revision    | string  | The recorded revision.    |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/honeybadger.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
