> 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.md).

# Workflow and Automation

This category covers workflow automation platforms, project management tools, and communication services. These integrations allow alerts to reach ITOC360 from business applications and automation pipelines — extending on-call coverage beyond traditional infrastructure monitoring.

***

### Integrations in this category

| Integration       | What it monitors or triggers                             | Alert delivery |
| ----------------- | -------------------------------------------------------- | -------------- |
| **Zapier**        | Automated workflow triggers from 5,000+ connected apps   | Webhook        |
| **n8n**           | Self-hosted workflow automation events and failures      | Webhook        |
| **Jira**          | Issue creation, status transitions, priority escalations | Webhook        |
| **Twilio**        | Programmable communications errors and alert events      | Webhook        |
| **MongoDB Atlas** | Database performance, replica set health, cluster alerts | Webhook        |
| **Salesforce**    | CRM workflow failures, critical record events            | Webhook        |

***

### How it works

Workflow and automation platforms generate events when business processes fail, data conditions are met, or integrations break. These events are forwarded to ITOC360 via webhook, where they are matched against escalation policies and routed to the on-call engineer. This allows teams to extend incident management beyond infrastructure — covering business-critical applications and automated pipelines.

{% hint style="info" %}
ITOC360 generates a unique webhook URL per Source. Go to **Management › Alert sources**, create a Source, and paste the webhook URL into your automation platform's outbound webhook or action settings.
{% endhint %}

***

### Get started


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itoc360.com/integrations/inbound-integrations/workflow-and-automation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
