> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/integrations-guideline/integrate-spike-with-bugsnag.md).

# Integrate Spike with Bugsnag

### Service and integration

With Bugsnag integration, you can -

* Add unlimited Bugsnag integrations for each of your checks in different services
* Receive error alerts for all projects when logged on Bugsnag
* Monitor your business for all clients including tvOS
* Segment and get alerts for the right errors
* Alert the right person/team with multiple Bugsnag integrations across your services

Make sure to add the Bugsnag integration and copy the webhook.

{% content-ref url="/pages/-Ln3rb4wLUFeI-OAPcmq" %}
[Create integration and service on our dashboard](/integrations-guideline/create-integration-and-service-on-dashboard.md)
{% endcontent-ref %}

## Using the Webhook with Bugsnag

### Step 1

Choose your project and goto **Settings.** Choose **Data Forwarding** to view all the options.

![](/files/-MClvEbkvKjf7a6X3CzV)

### Step 2

Choose **Webhook** and paste the Spike Webhook URL

![](/files/-MClvJbDp0ImBUTmoAsI)

{% hint style="success" %}
This integration auto resolves it's incidents
{% endhint %}

## FAQ

1. **How many services and integrations can I create on Spike?**
   * Unlimited
2. **How many escalation policies can I have on Spike?**
   * Unlimited

At Spike, we are working hard to integrate with all the tools your business uses. We are on a mission to help **you** identify incidents/crashes/spikes before your customers do.

If you have any integration in mind and would like us to build it for you then contact us at [support@spike.sh.](mailto:support@spike.sh)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spike.sh/integrations-guideline/integrate-spike-with-bugsnag.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.