> For the complete documentation index, see [llms.txt](https://docs.pagerly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pagerly.io/incidents-and-alerting/integrations/bugsnag.md).

# BugSnag

Create Pagerly incidents automatically from BugSnag errors.

### Create the integration in Pagerly

1\. Navigate to <https://workspace.pagerly.io/inbound> and click **"Add Alert Integration"**.

2\. Set a display name, select the team this integration belongs to, choose the integration below, and click **"Add Integration"**.

3\. Copy the generated webhook URL - you will paste it into the tool in the next section.

### Configure BugSnag

1\. In BugSnag open the project and go to **Settings → Data forwarding**.

2\. Enable the **Webhook** integration and paste the Pagerly webhook URL.

3\. Choose which events forward - typically **new error** and **error state change**.

BugSnag's payload is fixed, so there is nothing to paste.

### Notes

* **Deduplication** uses `error.errorId`, so repeated occurrences of the same error update one incident.
* **Severity** comes from `error.severity`: `error` maps to SEV 1, `warning` to SEV 2, `info` to SEV 3.
* **Resolution** comes from `error.status`, not the trigger: `fixed`, `snoozed` and `ignored` all resolve the incident, `open` keeps it open.


---

# 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.pagerly.io/incidents-and-alerting/integrations/bugsnag.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.