Skip to main content

Webhooks & Events

This guide explains the Cloudaware webhook and event-driven automation model.

Incoming Webhooks​

Cloudaware uses incoming webhooks to ingest alerts and notifications from external systems and store them as Cloudaware Incident object in CMDB.

Using incoming webhooks, Cloudaware can:

  • Accept alert notifications from monitoring and observability tools.
  • Convert those notifications into Cloudaware Incident records for tracking and response.
  • Normalize alerts from multiple sources into a consistent Cloudaware Incident format for operational visibility.
  • Preserve alert context from the source system, such as severity, resource name, affected service, timestamp, description, and source URL.

Common Use Cases For Webhooks​

Typical use cases include:

  • Centralizing alerts from multiple systems in one place.
  • Creating a handoff point from external detection tools into Cloudaware for incident management.
  • Supporting integrations where the monitoring platform sends the alert and Cloudaware receives it through a webhook endpoint.

How Webhooks Work​

An external system detects an issue and posts the event to Cloudaware’s webhook URL. Cloudaware then converts the event into an incident record for operational visibility.

For supported incoming webhook integrations, see Webhook Integrations.

Event-Driven Automation​

Cloudaware events can notify external systems, trigger workflows, and connect Cloudaware activity to ticketing, messaging, remediation, or orchestration tools.

Through using flows and outbound messages, Cloudaware can:

  • Forward resource-state alerts, like cloud service issues or monitoring thresholds, into external systems.
  • Enrich alerts & notifications with CMDB data for cross-reference deeper analysis.

Common Automation Scenarios​

Typical use cases include:

  • Creating tickets automatically when Cloudaware detects a resource state change, policy violation, vulnerability, or operational issue.
  • Routing events by ownership or business context using CMDB data, such as application, environment, team, account, region, or service owner.
  • Escalating high-priority events based on severity, affected resource type, production status, or compliance impact.
  • Starting remediation workflows when Cloudaware detects known issues.
  • Synchronizing status updates between Cloudaware and external ticketing or incident management systems.

How Automation Works​

When configured criteria are met, Cloudaware uses Salesforce Flows to trigger actions in external systems, such as creating an incident, issue, or ticket.

For supported outbound notification integrations, see Webhook Integrations.