# Zapier Integration

Zapier is a no-code automation platform that connects thousands of apps through workflows called Zaps. Each Zap consists of a trigger — an event in one app — followed by one or more actions that run automatically in response. By adding a webhook action to any Zap, you can forward alert data from virtually any source directly into ITOC360, without writing a single line of code.

### In ITOC360

Go to Sources, click **Create Source**, and select **Zapier** from the list. Once the source is created, copy the webhook URL and token from the source detail page — you will need these when configuring your Zap.

### In Zapier

#### Step 1 — Create a new Zap

Click the **+ Create** button in the top left corner and select **Zaps** from the dropdown.\ <br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FxxIGHKeaFW6TdbX7lpC8%2Fimage.png?alt=media&#x26;token=87bc90b5-b61e-484d-b1f0-351c00e47a78" alt=""><figcaption></figcaption></figure>

#### Step 2 — Set up your trigger

Click the **Trigger** step and choose whatever app and event makes sense for your workflow — this could be a new alert in a monitoring tool, a failed deployment, a form submission, or anything else. For testing purposes, **Schedule by Zapier** with **Every Hour** works fine.\ <br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2Fwhshym2Ar7ypLspl9jYn%2Fimage.png?alt=media&#x26;token=c3b38645-76b4-4c2f-94e0-d756143fcd5b" alt=""><figcaption></figcaption></figure>

#### Step 3 — Add a Webhooks by Zapier action

Click the **Action** step, search for **Webhooks by Zapier**, and select **POST** as the event. In the **Configure** tab, fill in the following fields:

**URL** — paste your ITOC360 webhook URL with your source token appended:

```
https://<url>?token=<your-token>
```

**Payload Type** — select **Json**

**Data** — add the following key-value pairs, mapping values from your trigger step as needed:

| Key        | Value                                              |
| ---------- | -------------------------------------------------- |
| `title`    | The alert title (e.g. from your trigger)           |
| `status`   | `trigger` for new alerts, `resolve` for recoveries |
| `message`  | A description of what happened                     |
| `id`       | A unique identifier for deduplication              |
| `severity` | `critical`, `high`, `medium`, or `low`             |

Make sure **Wrap Request In Array** is set to **No**.\ <br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FVSjTFJ0qYDptcB93VYVr%2Fimage.png?alt=media&#x26;token=38ab5e14-41fd-4e67-95a7-8ff3a54cd12a" alt=""><figcaption></figcaption></figure>

#### Step 4 — Test and publish

Click **Continue** to run a test. If ITOC360 responds successfully, your Zap is ready. Click **Publish** to activate it.\ <br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FIwyk4kIVdI2K4h5NJr1F%2Fimage.png?alt=media&#x26;token=a25c6a82-d019-4e1e-858f-b20cc04c4236" alt=""><figcaption></figcaption></figure>

### Notes

* The `id` field is used by ITOC360 to match an alert with its resolution. Make sure the same `id` value is sent in both the trigger and resolve payloads — without it, ITOC360 falls back to using the `title` field for deduplication.
* To resolve an alert, create a separate Zap (or add a path) that sends the same payload with `status` set to `resolve` and the same `id`.
* The `title` and `status` fields are required. All other fields are optional but recommended for richer alert context.
* Webhooks by Zapier is available on paid Zapier plans.