> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/integrations/inbound-integrations/workflow-and-automation/zapier-integration.md).
# Zapier Integration
[Zapier](https://zapier.com/) 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 in response.
ITOC360 has a native Zapier app, so you can pick **ITOC360** as an action in any Zap and route events from thousands of tools straight into your on-call pipeline. No webhook URLs to copy around, no JSON to hand-craft — connect once with a source token and map your fields.
### In ITOC360
Go to **Sources**, click **Create Source**, and select **Zapier** from the list. Once the source is created, open its detail page and copy the **token** — you will paste it into Zapier in a moment.
### In Zapier
#### Step 1 — Create a new Zap
Click the **+ Create** button in the top left corner and select **Zaps** from the dropdown.
> **Want to skip setup?** Use our ready-made template: [Send daily heartbeat alerts to ITOC360](https://zapier.com/apps/itoc360/integrations/schedule/255731674/send-daily-heartbeat-alerts-to-itoc360) — it creates the Zap with all fields pre-configured; you only connect your ITOC360 account.
#### Step 2 — Set up your trigger
Choose whatever app and event fits your workflow — a failed deployment, a form submission, a new row in a spreadsheet, or anything else. For a quick test, **Schedule by Zapier** works fine.
#### Step 3 — Add the ITOC360 action
Click the **Action** step and type **ITOC360** into the search box. Select the ITOC360 app, then pick **Send Alert** as the event.
#### Step 4 — Connect your ITOC360 account
When prompted, click **Connect** and paste the source token you copied earlier. That's the only credential Zapier needs — one connection can be reused across all your Zaps.
#### Step 5 — Configure the alert
Fill in the fields, mapping values from your trigger step where it makes sense:
| Field | Description |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title**(required) | Short summary of the alert. |
| **Status**(required) | **Trigger (open alert)** to create a new alert, **Resolve** to close an existing one. |
| **Deduplication ID** | A stable identifier for the alert. Send the same value in the trigger and resolve payloads so ITOC360 can match them. If left empty, ITOC360 falls back to the title. |
| **Severity** | `Critical`, `High`, `Medium`, or `Low`. Defaults to `Medium`. |
| **Message** | A longer description with any context your on-call engineer will thank you for. |
#### Step 6 — Test and publish
Click **Test step**. If everything is wired up correctly, Zapier shows the created event in the **Data out** tab, and the alert appears in your ITOC360 dashboard within seconds. Click **Publish** to activate the Zap.
### Resolving alerts
To close an alert automatically, send a second event with **Status** set to **Resolve** and the same **Deduplication ID** as the original alert. You can do this from a separate Zap, or add a path within the same Zap that fires when your trigger reports recovery. ITOC360 correlates the two events and resolves the open alert.
### Notes
* One ITOC360 connection can be shared by any number of Zaps — you don't need a separate source per workflow.
* Events with the same deduplication ID are grouped together, so repeated triggers won't flood your on-call team with duplicates.
* The ITOC360 app is currently in beta on the Zapier App Directory. Everything is fully functional; the badge just means we're gathering usage before the official listing.
### Alternative: Webhooks by Zapier
If you prefer working with raw webhooks — or you're on a Zapier workflow that already uses them — you can still send events through the generic **Webhooks by Zapier** action instead of the native app.
Add a **Webhooks by Zapier** action with **POST** as the event, and configure it as follows:
**URL** — your ITOC360 webhook URL with the source token appended:
```
https://api.itoc360.app/functions/v1/events?token=
```
**Payload Type** — `Json`
**Data** — the following key-value pairs:
| Key | Value |
| ---------- | ------------------------------------------------------------- |
| `title` | The alert title (required) |
| `status` | `trigger` for new alerts, `resolve` for recoveries (required) |
| `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**.
Note that Webhooks by Zapier is only available on paid Zapier plans, while the native ITOC360 action works on every plan — one more reason to prefer the app.
---
# 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.itoc360.com/integrations/inbound-integrations/workflow-and-automation/zapier-integration.md?ask=&goal=
```
`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.