Inbound Integrations

ITOC360 receives alerts from your existing monitoring, observability, security, and DevOps tools through inbound integrations. Each integration connects to ITOC360 via a webhook-based Source, allowing alerts to flow into your escalation policies automatically.

---

Integration categories

Browse integrations by category to find setup instructions for your tools:

Infrastructure Monitoring

Zabbix, PRTG, SolarWinds, ManageEngine OpManager, CheckMK, Instana

infrastructure-and-network-monitoring.md

Observability and APM

Grafana, Prometheus, Datadog, New Relic, Dynatrace, AppDynamics, and more

observability-and-apm.md

Cloud Monitoring

AWS CloudWatch, AWS Budget, Google Cloud Monitor, Azure Monitor, Alibaba CloudMonitor

cloud-monitoring.md

Log Management

Grafana Loki, Grafana Mimir, Graylog, InfluxDB

log-management.md

Security

AWS GuardDuty, Azure Sentinel, Google Security Command Center, CrowdStrike

security.md

DevOps and CI/CD

ArgoCD, Azure DevOps, GitHub, GitLab, Jenkins, Terraform Cloud

devops-and-cicd.md

Error Tracking and Uptime

Sentry, Rollbar, Pingdom, StatusCake, Postman, Statuspage.io

error-tracking-and-uptime.md

Workflow and Automation

Zapier, n8n, Jira, Twilio, MongoDB Atlas, Salesforce

workflow-and-automation.md

---

How inbound integrations work

Every inbound integration connects to ITOC360 through a Source. When you create a Source in Management > Sources, ITOC360 generates a unique webhook URL and token. You paste this into your external tool's notification or alerting settings. From that point, alerts are sent to ITOC360 automatically whenever your tool fires one.

Incoming alerts are matched against your active escalation policies. If a match is found, ITOC360 creates an incident and notifies the assigned on-call engineer.

Any tool that supports outbound HTTP webhooks can connect to ITOC360, even if it is not listed in the categories above. Use the Custom Webhook option when creating a Source.