Webhooks (Slack & Teams)

Integrate Keeper Webhook events into Slack, Microsoft Teams and other cloud services.

What are Webhooks?

Webhooks are user-defined HTTP requests that are triggered by an application and pushed into other applications.

Popular uses of Webhooks are the following:

  • Sending realtime notifications to Slack, Microsoft Teams or other messaging platforms

  • Integrating Keeper events into your custom software, hosted in the Cloud

  • Developing integrations into Keeper using 3rd party platforms such as IFTTT

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 page for list of all possibilities.

#timestamp

Time which the event occurred

#remote_address

External IP address of the user generating the event

#username

User who generated the alert or could 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 into various areas of the Keeper platform. A few examples:

Vault Login URL:

  • US: https://keepersecurity.com/vault

  • EU: https://keepersecurity.eu/vault

  • AU: https://keepersecurity.com.au/vault

  • CA: https://keepersecurity.ca/vault

  • JP: https://keepersecurity.jp/vault

  • US_GOV: https://govcloud.keepersecurity.us/vault

Admin Console URL:

  • US: https://keepersecurity.com/console

  • EU: https://keepersecurity.eu/console

  • AU: https://keepersecurity.com.au/console

  • CA: https://keepersecurity.ca/console

  • JP: https://keepersecurity.jp/console

  • US_GOV: https://govcloud.keepersecurity.us/console

Keeper supports Deep Linking into the Web Vault for a particular Record UID. Example:

https://keepersecurity.com/vault/#detail/XXXXXX

  • replace XXXXXX with the Record UID as it appears in the Keeper record or substitute #record_uid

  • Make sure to replace .com with the proper domain as listed above

Platform-Specific Guides

We have documented a few examples for popular endpoints below.

Last updated