> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/webhooks.md). # Webhooks Integrate Keeper Webhook events into Slack, Microsoft Teams and other cloud services. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fgit-blob-f0803513a3c68ece7ce6467f4ea6a6a321135f9d%2Fwebhooks-header-v2.png?alt=media) ## What are Webhooks? Webhooks are user-defined HTTP requests that are triggered by an application and pushed to other applications. Popular uses of Webhooks are the following: * Sending real-time notifications to **Slack**, **Microsoft Teams,** or other messaging platforms * Creating tickets in ITSM platforms like **ServiceNow** and **Jira** * Integrating Keeper events into your custom software, hosted in the cloud The Keeper Admin Console supports the ability to push custom Webhook events. ## Global Event Variables When sending a Webhook, you can substitute fields with one of the below variables. | Name | Description | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | #alert\_name | Title of the event as appears in the Admin Console | | #description | Description of the event. See [Reporting & Alerts](/enterprise-guide/event-reporting.md#event-list) page for list of all possibilities. | | #timestamp | Time when the event occurred | | #remote\_address | External IP address of the user generating the event | | #username | User who generated the alert (may be empty depending on the event) | | #json | Raw JSON event data (useful for debugging and inspecting fields) | ## Dynamic Event Variables Depending on the type of event, there are other variable substitutions available. | Name | Description | | -------------------- | ------------------------------------------------- | | #to\_username | For sharing events, the destination user | | #from\_username | For sharing events, the source user | | #record\_uid | For Record events, the Record identifier | | #shared\_folder\_uid | For Shared Folder events, the folder identifier | | #folder\_uid | For Folder-specific events, the folder identifier | | #team\_uid | For Team events, the Team identifier | | #role\_id | For Role events, the Role ID | | #node | For Node events, the Node ID | | #enforcement | For Role Policy changes, the enforcement name | | #seats | For MSP events, the number of seats | | #seats\_added | For MSP events, the number of seats added | | #seats\_removed | For MSP events, the number of seats removed | ### URLs You can also include hyperlinks for convenience to various areas of the Keeper platform. A few examples: Vault Login URLs: * **US:** * **EU:** * **AU:** * **CA:** * **JP:** * **US\_GOV:** Admin Console URLs: * **US:** * **EU:** * **AU:** * **CA:** * **JP:** * **US\_GOV:** ### Deep Links Keeper supports Deep Linking into the Web Vault for a particular Record UID. Example: * Replace XXX with the Record UID as it appears in the Keeper record or substitute `#record_uid` * Replace `.com` with the proper tenant domain * `.com` for US * `.eu` for EU * `.com.au` for AU * `.ca` for CA * `.jp` for JP * `.us` (with `govcloud.` subdomain) for GovCloud ### Platform-Specific Guides We have documented a few examples for popular endpoints below. * [Slack](/enterprise-guide/webhooks/slack-webhooks.md) * [Microsoft Teams](/enterprise-guide/webhooks/teams-webhooks.md) * [Discord](/enterprise-guide/webhooks/discord-webhooks.md) * [ServiceNow ITSM](/keeperpam/secrets-manager/integrations/servicenow-itsm.md) * [Jira ITSM](/keeperpam/secrets-manager/integrations/jira-itsm.md) --- # 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.keeper.io/enterprise-guide/webhooks.md?ask=&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.