# FAQ

<details>

<summary>What is the difference between the Errors and Events entities?</summary>

**Errors** are grouped occurrences of the same exception — Bugsnag deduplicates individual crashes into a single error record with aggregate stats (total count, unique users, first seen, last seen). **Events** are the individual, raw crash reports that make up those errors. Use Errors for trend analysis and dashboards; use Events when you need per-occurrence details like stack traces, device info, or user breadcrumbs.

</details>

<details>

<summary>Where do I find my Bugsnag API key?</summary>

You need your **Personal Auth Token**, not the project API key. Log into Bugsnag, click your avatar in the top right, go to **My Account**, and scroll to the **Personal auth token** section. The project API key (shown in project settings) is for SDK instrumentation and won't work with Coupler.io.

</details>

<details>

<summary>Can I pull data from multiple Bugsnag projects in one data flow?</summary>

Yes — add multiple sources within the same data flow, each pointing to a different project. Then use the **Append** transformation to combine them into a single output table. This is useful for cross-project stability reports or portfolio-level dashboards.

</details>

<details>

<summary>Why is my Events export so slow or timing out?</summary>

The Events entity returns raw, per-occurrence data which can be very large for active projects. Narrow your start date to a shorter window (start with 7 days) and confirm the flow works before expanding. Also check that your Bugsnag plan supports the API rate limits needed for bulk event exports.

{% hint style="info" %}
See [Common Issues](https://docs.coupler.io/sources/category/other/bugsnag/common-issues) for more on rate limits and large export handling.
{% endhint %}

</details>

<details>

<summary>Can I use Bugsnag data with AI tools like ChatGPT or Gemini?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Bugsnag Errors or Events data directly to these tools for AI-generated analysis — for example, asking an AI to summarize the top error trends or suggest fixes based on error messages.

</details>

<details>

<summary>What permissions does my Bugsnag account need?</summary>

It depends on which entities you're exporting. Project-scoped entities like Errors, Events, and Releases only require project member access. Organization-level entities — Organizations, Collaborators, and Teams — require **Organization Admin** permissions. If you're getting 403 errors, check your role in Bugsnag.

{% hint style="info" %}
See [Common Issues → Permission errors](https://docs.coupler.io/sources/category/other/bugsnag/common-issues) for troubleshooting steps.
{% endhint %}

</details>

<details>

<summary>How do I track which app version caused a spike in errors?</summary>

Export both the **Errors** and **Releases** entities as separate sources in your data flow, then use Coupler.io's **Join** transformation to link them by app version. This lets you see error counts and severity alongside release metadata — including which release stage and build tool was used.

{% hint style="info" %}
See [Data Overview → Common metric combinations](https://docs.coupler.io/sources/category/other/bugsnag/data-overview) for more on joining Bugsnag entities.
{% endhint %}

</details>

<details>

<summary>Does Coupler.io support incremental syncs for Bugsnag?</summary>

Coupler.io uses your configured start date to determine how far back to fetch data on each run. For ongoing refreshes, set a start date that reflects your desired lookback window. Each scheduled run will pull data from that date forward, keeping your destination up to date.

</details>