Zoho Vault Webhook Setup Guide

Open the linked account in StackOne and copy the Native Webhook URL with the copy icon.

• It is available once the account is connected.
• Every Vault webhook below uses this same URL.

Sign in to your Zoho Vault account as a Super Admin.

• Click Settings, then Webhook Integration under Integrations.
• Click Create Webhook, or Add when webhooks already exist.

In Create Webhook, enter a Webhook Name such as StackOne Passwords, keep Method as POST and paste the Native Webhook URL into Webhook URL.

• Keep Module as Passwords for this first webhook.
• Under Trigger Events, click Select All.

Under URL Parameters, select Send custom json and replace the box contents with the payload for the module, then click Create Webhook.

• StackOne routes each event by its OperationType field, so keep the payload exactly as shown.
• Vault checks the URL when the webhook is created and StackOne answers that check automatically.

Paste this payload for the Passwords module.

{"OperationType": "${OperationType}", "PasswordId": "${PasswordId}", "PasswordName": "${PasswordName}", "CategoryId": "${CategoryId}", "CategoryName": "${CategoryName}", "OwnerUserId": "${OwnerUserId}", "UserName": "${UserName}", "UserId": "${UserId}", "UserEmail": "${UserEmail}", "Timestamp": "${Timestamp}"}

Click Add again for each other module, pick it under Module, click Select All and paste its payload.

• Folder (name it StackOne Folders)
• Users (name it StackOne Users)
• Apps (name it StackOne SSO Apps)

Folder:

{"OperationType": "${OperationType}", "FolderId": "${FolderId}", "FolderName": "${FolderName}", "OwnerUserId": "${OwnerUserId}", "UserName": "${UserName}", "UserId": "${UserId}", "UserEmail": "${UserEmail}", "Timestamp": "${Timestamp}"}

Users:

{"OperationType": "${OperationType}", "OperatedOnUserId": "${OperatedOnUserId}", "OperatedOnUserName": "${OperatedOnUserName}", "OperatedOnUserEmail": "${OperatedOnUserEmail}", "UserStatus": "${UserStatus}", "UserName": "${UserName}", "UserId": "${UserId}", "UserEmail": "${UserEmail}", "Timestamp": "${Timestamp}"}

Apps:

{"OperationType": "${OperationType}", "AppId": "${AppId}", "AppName": "${AppName}", "AppStatus": "${AppStatus}", "UserName": "${UserName}", "UserId": "${UserId}", "UserEmail": "${UserEmail}", "Timestamp": "${Timestamp}"}

New webhooks start switched off. Turn on the Status toggle of each webhook you created.

• Vault turns a webhook off after 5 failed deliveries in a row. Turn it on again from the same toggle.

Vault verifies the URL when a webhook is created or turned on.

• Active Check (url_verification) — Fired when Vault checks the webhook URL; StackOne answers it so Vault can enable the webhook

Events from the Passwords module.

• Password Added (password.added) — Fired when a password is created
• Password Updated (password.updated) — Fired when a password is edited
• Password Deleted (password.deleted) — Fired when a password is deleted
• Password Viewed (password.viewed) — Fired when a user reveals a password in Vault
• Password Checked Out by User (password.checked_out) — Fired when a user checks out a password under access control
• Password Checked-In (password.checked_in) — Fired when a checked-out password is checked back in
• Password Acquired (password.acquired) — Fired when an admin takes ownership of a password
• Access Request Created (access_request.created) — Fired when a user requests access to a password
• Access Request Approved (access_request.approved) — Fired when an access request is approved
• Access Request Rejected (access_request.rejected) — Fired when an access request is rejected
• Category Added (category.added) — Fired when a password category is added
• Category Updated (category.updated) — Fired when a password category is edited. In testing, Vault did not send this event
• Category Deleted (category.deleted) — Fired when a password category is deleted

Events from the Folder module.

• Folder Added (folder.added) — Fired when a folder is created
• Folder Updated (folder.updated) — Fired when a folder is edited
• Folder Deleted (folder.deleted) — Fired when a folder is deleted
• Folder Shared (folder.shared) — Fired when a folder is shared with users or user groups
• Folder Shared To Third Party (folder.shared_to_third_party) — Fired when a folder is shared with an outside party
• Folder Acquired (folder.acquired) — Fired when an admin takes ownership of a folder

Events from the Users module.

• Users Invited (users.invited) — Fired when users are invited to the organization
• Users Added (users.added) — Fired when users join the organization
• Users Deleted (users.deleted) — Fired when users are deleted
• Users Role Changed (users.role_changed) — Fired when a user’s role changes

Events from the Apps module.

• SSO App Added (sso_app.added) — Fired when an SSO app is added
• SSO App Updated (sso_app.updated) — Fired when an SSO app is edited
• SSO App Enabled (sso_app.enabled) — Fired when an SSO app is enabled
• SSO App Disabled (sso_app.disabled) — Fired when an SSO app is disabled
• SSO App Deleted (sso_app.deleted) — Fired when an SSO app is deleted
• SSO App User Mappings Updated (sso_app.user_mappings_updated) — Fired when the users mapped to an SSO app change. In testing, Vault did not send this event