Feature Overview

Webhooks allow you to forward notifications about incidents, activities, and events to external applications or services. To create a webhook, specify a name, a destination URL, optional secret, and a payload type. Then select the categories to send, such as incident severity levels or activity and event types. This ensures external applications receive only the notifications relevant to your needs.

Any application or service that accepts incoming webhook requests can receive notifications if it provides a valid webhook URL.

Webhooks provide real‑time communication between RUCKUS One and external systems by sending an HTTP POST to the specified endpoint whenever a predefined incident, activity, or event occurs. This mechanism ensures the receiving application is updated immediately without requiring scheduled polling or manual checks.

Administrators can use Webhooks to deliver operational, activity, or security‑related information to tools such as ServiceNow, Datadog, Microsoft Teams, Slack, Splunk, or other SIEM (Security Information and Event Management) systems. These integrations help centralize monitoring and improve responsiveness to network or service changes.

Webhook Configuration Templates extend this capability for MSPs. MSPs can create, update, clone, enforce, or delete templates. When a template is enforced, customers cannot change template‑controlled fields. The system tracks differences between templates and their instances and provides a Sync to keep configurations aligned. Webhook Templates let MSPs apply consistent settings across customer accounts.

Requirements

This feature has no special hardware or software requirements for feature enablement or usage.

Considerations

Consider the following when configuring and using this feature:

• Webhook Configuration Templates are created and managed by MSPs and applied to end‑customer accounts.
• Updating a template can affect multiple customers that depend on the template settings.
• Enforcing a template prevents customers from modifying template‑controlled webhook fields.
• Use Sync to keep template‑based configurations aligned with the current template version.
• The webhook name and webhook URL must be unique within an account.
• Each account can create up to 20 webhooks.
• When a Webhook Configuration Template is deleted, the webhooks created from that template remain in the customer accounts, but they are no longer treated as template‑based configurations.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

Complete the following before using Webhooks or Webhook Configuration Templates:

• Obtain a valid webhook URL from the external system you plan to integrate with.
• Identify the categories of information (Incidents, Activities, Events) that the external system should receive.
• Determine which MSP end-customer accounts should receive template‑based configurations.