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

# Zapier

Send your Adalysis alerts to Zapier and on to thousands of other apps

Connect Zapier, and every notification Adalysis sends becomes a trigger in a Zap. From there you can send it anywhere Zapier reaches: create a task in Asana or Jira, add a row to Google Sheets, post to a Discord channel, send an SMS, open a ticket in your help desk, and much more.

Zapier works alongside email and Slack. You decide which notifications go to Zapier, which go to email, which go to Slack, and which go nowhere.

**What you can send to Zapier**

* Performance monitor alerts (on Meta logins these include rule findings)
* Performance goal alerts
* Critical alerts (issues stopping your ads from running), for Google Ads and Microsoft Ads logins
* Routine tasks reminder, for Google Ads and Microsoft Ads logins
* Health alerts, for Meta logins
* Budget spend alerts
* Budget pacing alerts
* Budget rollover

Zapier also receives the notices Adalysis always sends, whatever is ticked: when it couldn't do something it was asked to do (for example, campaigns that couldn't be paused, budget changes that failed, or budget automation turned off because Google refused its changes), conversion set alerts, and connection alerts when a login loses access to its ad platform.

**Why this is useful**

* Turn alerts into work items automatically: a critical alert can open a ticket, and a budget alert can create a task for the account manager.
* Keep a log of every alert in a spreadsheet or database, ready for reporting.
* Reach the tools your team or your clients already use, even ones Adalysis doesn't connect to directly.

***

**Before you connect**

* The **Owner and Admins** can add and remove Zapier hooks and choose which hook each login uses. An Admin can only choose hooks for the logins they can open, and can't remove, test, or change a hook that also serves logins they don't manage.
* You'll need a Zapier plan that includes **Webhooks by Zapier**.
* **Each event Adalysis sends counts as a task on your Zapier plan.** To keep your task usage down, only tick the notifications you actually need in each login's Notifications settings (step 7 below).
* Each login sends to one hook, so you can, for example, give each client their own. An Adalysis account can have **up to 20 notification destinations** in all (Zapier hooks, Microsoft Teams workflows, webhooks, and Google Chat spaces together; Slack channels don't count).

***

**Setting it up**

1. In Zapier, create a new Zap. For the trigger, choose **Webhooks by Zapier** and the event **Catch Hook**.
2. Copy the webhook URL Zapier shows you. It starts with `https://hooks.zapier.com/hooks/catch/`.
3. Open your **Adalysis account** (the tile at the top of the rail on the left) and go to **Notifications**. On the **Notification destinations** card, click **Add a Zapier hook**.

   ![Open your Adalysis account (1), Notifications (2), then Add a Zapier hook (3)](https://3203600314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGlXujWJyreRidNjZDCw2%2Fuploads%2FKSsDB5uA1ToNtzni086C%2FZP-01.png?alt=media)
4. Give it a name (for example, the name of its Zap), paste the URL as the **Catch Hook URL** and click **Add**.

   ![Add a Zapier hook: a name (1), the Catch Hook URL (2), then Add (3)](https://3203600314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGlXujWJyreRidNjZDCw2%2Fuploads%2FTO6MHaUu1AJJPXOrgIlo%2FZP-02.png?alt=media)
5. Adalysis sends a test first. If Zapier refuses it, the hook isn't added and you'll see why. If Zapier can't be reached at that moment, the hook is added anyway, and you'll be asked to send it a test event later. Back in Zapier, click **Test trigger** to load the test event, then map its fields in your Zap's next steps.
6. Under **Ad platform logins**, the new hook is already chosen in the **Zapier** column for every login that didn't have one. To change a login's hook, or turn it off with **No Zapier**, choose it and click the **Save** next to it.

   ![Ad platform logins: the login's hook (1) and its Save (2)](https://3203600314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGlXujWJyreRidNjZDCw2%2Fuploads%2Fd2lG7mekQNNE1iDFT6JC%2FZP-04.png?alt=media)
7. Open each login in the app, go to **Settings** > **Notifications** and tick the **Zapier** column for each notification you want sent there, then click **Save**. On a team, only the login's main user can change this column; other team members see it read-only.

Scheduled notifications arrive at the delivery time and time zone set in the login's **Settings** > **Notifications**. Budget alerts are sent as soon as they happen.

{% hint style="info" %}
**Tip: build your Zap from a real example.** Each hook on the **Notification destinations** card has a list of examples (for example, *Example: Budget pacing alerts*) and a **Send test event** button. Send an example of each kind of notification your Zap will handle, so every field is available to map. Use a **Filter** step on the `event_type` field to handle different notifications differently.
{% endhint %}

![A hook's row: pick an example (1), then Send test event (2). Its last delivery, and any problem, show under its name](https://3203600314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGlXujWJyreRidNjZDCw2%2Fuploads%2Fc7kmFBhB8HmTsJBPGB5R%2FZP-03.png?alt=media)

***

**What Zapier receives**

Adalysis sends one event per notification and ad account. The exceptions are the routine tasks reminder, which is sent once per login, and connection alerts, which are sent once per login that lost its connection. Every field is always present (set to empty when it doesn't apply), so your Zap's mapping doesn't break from one event to the next.

| Field                                                    | What it holds                                                                                             |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| `event_type`                                             | The kind of notification, for example `budget_pacing_alert`. Use this in Filter and Paths steps.          |
| `event_label`                                            | Its readable name, for example *Budget pacing alerts*                                                     |
| `title`, `text`                                          | A ready-to-use headline and plain-text summary                                                            |
| `url`                                                    | A link to the right screen in Adalysis                                                                    |
| `platform`                                               | `google`, `microsoft`, or `meta`                                                                          |
| `account.name`, `account.display_id`, `account.currency` | The ad account the notification is about                                                                  |
| `login.email`                                            | The login it came from                                                                                    |
| `items`                                                  | The rows of the notification (campaigns, budgets, alerts…), up to 200; `item_count` gives the full number |
| `test`                                                   | `true` for test events, so you can filter them out                                                        |
| `dedupe_key`                                             | The same for repeats of one notification on one day, useful for skipping duplicates                       |

The full list of fields and `event_type` values is on the [Webhook](https://docs.adalysis.com/integrations/webhook.md) page. Zapier receives exactly the same data.

***

**Changing or removing a hook**

To send a login to a different Zap, choose the new hook for that login under **Ad platform logins** and click **Save**. To stop using a hook, click **Remove** next to it.

If the Zap is turned off or deleted, or its trigger is changed, Zapier stops accepting events and the hook shows **Zapier stopped accepting it: send a test event once it is fixed** on the **Notification destinations** card. The account's owner gets an email about it. Turn the Zap back on (or add the new hook) and click **Send test event** to reconnect it.

Note: Zapier keeps accepting events for a few hours after a Zap is turned off or deleted. If a test event is accepted but doesn't show in your Zap, check that the Zap is turned on.

For everything else, such as delivery time, email address, and which accounts you get notified about, see [Notifications](https://docs.adalysis.com/onboarding/getting-started/core-account-settings/notifications).
