# Integration events

"Why didn't this call reach Google Ads?" Integration events answer it. For each call or form, you can see which workflows ran, which filter stopped the ones that didn't, and exactly what Nimbata sent to each integration, with the integration's reply.

You can look at it two ways: call by call, from a call's or form's details, or for a whole project at once, under **Workspace › Integration Events**.

**Before you start**

- Plan: Agency
- Permissions: Audit Log & Integration Events (read), in your project role
- A workflow that sends calls or forms to an integration.

## See why a workflow did or didn't run for a call

1. **Open the call**

   Go to **Activity › Calls** and click the call. For a form, go to **Activity › Forms** and click the submission.

2. **Open the Workflows tab**

   Next to **Call Data**, **Attribution** and **Transcript**, the details have two more tabs: **Integrations** and **Workflows**. Open **Workflows** (1).

   Each run is listed with what started it (such as **Call ended** or **Transcription ready**) and when it ran. Under each run, every workflow shows its steps in order:

   - A **Filter** step says **true** when the call passed it, **false** when it stopped the call, or **not reached**.
   - An **Actions** step says **executed**, **waiting**, **pending** or **skipped**.

   The filter that stopped a workflow is the one marked **false**: the steps after it are dimmed, because they never ran.

   [A call's Workflows tab, marked 1: the Call ended run with two workflows. Google Ads Call Conversion passed its filter and its action was executed; Slack alert for long calls stopped at a Duration filter marked false, with its action dimmed]

   *The Workflows tab (1): the first workflow ran, the second stopped at its filter.*

3. **See what each integration received**

   Open **Integrations** for one card per integration the call was sent to. Each attempt shows its result and, when you expand them, the **Request payload** Nimbata sent, the **Response** it got back and the **Request details**.

If the call wasn't sent anywhere, the tabs say "No integrations were executed for this call." and "No workflows ran for this call."

Detailed guide: [How workflows decide what runs](https://help.nimbata.com/workflows/workflow-logic)

## Review every delivery in a project

1. **Open Integration Events**

   Go to **Workspace › Integration Events**. You see every delivery attempt for the project selected at the top of the app, newest first, grouped by day. Pick **All Projects** in the project selector to see all your projects together. **Load more** shows older events.

2. **Filter the list**

   Narrow the list with the search box (1), which finds a subject or configuration ID, and with **All integrations** and **All statuses** (**Success**, **Failed** or **Queued**). **Clear filters** resets them, and the refresh button reloads the list.

   [The Integration Events page: the search box marked 1, the All integrations and All statuses filters, the list of events grouped under Queued and Today, and the selected Google Ads event's detail with its result, response code and request payload]

   *Search or filter the events (1), then pick one to see its request and response.*

3. **Open an event**

   Click an event to see its **Result**, **Response code**, time, **Integration**, **Project**, **Subject** and **Configuration**. For a call, a **Call details** block shows when it started, the caller, the tracking number, the destination, the outcome and the duration. Each attempt below can be expanded to show the **Request payload**, the **Response** and the **Request details**.

## What the statuses mean

- **Success**: the integration accepted what Nimbata sent.
- **Failed**: the integration refused it or didn't answer. The **Response** shows the integration's own error message, which usually names the fix (an expired connection, a missing field, a deleted conversion action).
- **Queued**: waiting to be sent. Google Ads conversions are uploaded 12 hours after the call or form, so they show under **Queued** until then, with the time they're due. If one is still queued after that time, the hourly upload keeps retrying it. If it stays queued, check your Google Ads setup.

There's no button to send an event again. Once you've fixed the cause, new calls are sent as usual.

## Frequently asked questions

### How far back can I see events?

Each event is kept for 365 days. After that, its request and response are deleted automatically.

### I can't see the Integrations and Workflows tabs on a call.

You need the Agency plan and a project role with read access to **Audit Log & Integration Events**. Without the plan, the tabs show a blurred preview and an upgrade button. Ask your account owner to check your role under [Users and roles](https://help.nimbata.com/account/users-and-roles).