Cisco Secure Access Help

Manage Webhooks for Third-Party Integrations

Updated: August 24, 2026

Want to summarize with AI?

Manage Webhooks to support notifications for alert rules and third-party integrations in Secure Access.

Organizations can add Webhooks in Secure Access that support notifications for alert rules or third-party integrations. A Secure Access Webhook sends notifications or messages to a configured destination URL for an integrated third-party product or service.

For example, set up a Webhook to send notifications about certain conditions on a specific type of Secure Access resource to a third-party Security Information and Event Management (SIEM) system. The organization is responsible for configuring any third-party products or services to receive the notifications.

Note

You can add a maximum of ten Webhooks in your Secure Access organization.

Guidelines for Configuring an HTTP Listener

Configure an HTTP listener (target service of the Webhook) in the organization's on-premises or cloud environment.
Ensure that the target service accepts Basic authentication for HTTP POST API requests. You will set up the Secure Access Webhook with the username and password for an account on the target service.

Add a Webhook for a Third-Party Integration

Add a Webhook in Secure Access. A configured Webhook sends notifications to an integrated third-party product or service.

Before you begin

Full Admin user role. For more information, see Manage Accounts.

Procedure

Navigate to Admin > Third-party Integrations and then click Webhooks.
Click + Webhook.
1. For Webhook name, enter 2–250 alphanumeric, underscore, or hyphen characters. Choose a meaningful name that describes the Webhook.
2. For Address/Destination URL, enter the URL for the HTTP listener that you deployed in your environment.
3. For Authentication method, Secure Access supports Basic authentication.
4. For Username, enter the name for the user account that Secure Access will use to authenticate the API request to the target service.
5. For Password, enter the password for the user account that Secure Access will use to authenticate the API request to the target service.
Click Save.

View Details for Webhooks

View the Webhooks in Secure Access and the details for each configured Webhook.

Before you begin

A minimum user role of Read-only. For more information, see Manage Accounts.

Procedure

Navigate to Admin > Third-party Integrations and then click Webhooks.
Secure Access displays the list of configured Webhooks and the details for each Webhook added in the organization.
- Name—The name of the Webhook.
- Used by—The name of the Third-party Integration that is associated with the Webhook.
- Added by—The organization ID and user account that added the Webhook.
- Status—The state of the Webhook, either active or inactive.
- Added on—The date and time when the organization added the Webhook.
To view the details for a Webhook, navigate to the Webhooks table, and then click on the name of a Webhook.

Secure Access displays the details about the Webhook and the Third-party integration associated with the Webhook.
1. Navigate to General Details.
  - Webhook name—The name of the Webhook.
  - Address/Destination URL—The address of the HTTP listener assigned to the Webhook.
  - Authentication method—The method of authentication used in the API request by the Webhook.
  - Added by—The organization ID and user account that added the Webhook.
  - Added on—The date and time when the organization added the Webhook.
2. Navigate to Used by.
  - Name—The name of the Third-party Integration.
  - Type—The type of the Third-party Integration.
  - Status—The state of the Third-party Integration, either active or inactive.
Click Close.

Edit a Webhook for a Third-Party Integration

In Secure Access, edit a Webhook that is configured to send notifications to an integrated third-party product or service.

Before you begin

Full Admin user role. For more information, see Manage Accounts.

Procedure

Navigate to Admin > Third-party Integrations and then click Webhooks.
Navigate to the Webhooks table, and then click on the name of a Webhook or the pencil icon at the end of a row.

Note

You can modify the Webhook name and destination URL only.
1. For Webhook name, enter 2–250 alphanumeric, underscore, or hyphen characters. Choose a meaningful name that begins with an alphanumeric character.
2. For Address/Destination URL, enter the URL for the HTTP listener that you deployed in your on-premises or cloud environment.
Click Save.

Delete a Webhook for a Third-Party Integration

In Secure Access, delete a Webhook that is configured to send notifications to an integrated third-party product or service.

Note

You can delete a Webhook that is associated with an integration.

Before you begin

Full Admin user role. For more information, see Manage Accounts.

Procedure

Navigate to Admin > Third-party Integrations and then click Webhooks.
Navigate to the Webhooks table, and then click on the name of a Webhook or the trash can icon at the end of a row.
In the dialog window, click Delete to confirm the removal of the Webhook.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.