If you’re using Voiceflow within a larger organization, you might want to integrate with your existing observability or testing tools. Organization events webhooks let you automatically receive updates whenever something happens in your organization - for example, when a new project is created. Just provide a webhook URL, and Voiceflow will send event data there in real time.
Configuring your webhook settings
If you’re less technical, we recommend using a tool like Make to generate a webhook URL and run automations. If you’re a developer, you can hook into your existing infrastructure using any tool that can receive and process JSON payloads.
To enable sending data to a webhook whenever key events happen within an organization, head to your Voiceflow dashboard, click the Settings button in the bottom left corner, then select Organization. You can then add the URL that you’d like to send events to in the box provided.
Once you’ve set a webhook URL, all future events will be automatically sent to it.
Supported events
The following organization-level events will be sent to the provided URL:
organization.project.created
Sent when a new project is created in the organization.
Example organization.project.created payload
Example organization.project.created payload
organization.project.deleted
Sent when a project is deleted from the organization.
Example organization.project.deleted payload
Example organization.project.deleted payload
organization.project.environment.created
Sent when a new environment is created within a project. The source describes the environment the new one was branched from.
Example organization.project.environment.created payload
Example organization.project.environment.created payload
organization.project.environment.published
Sent when an environment within a project is published. publishedVersionIDBefore and publishedVersionIDAfter let you track what changed.
Example payload - publishing the live Main environment
Example payload - publishing the live Main environment
Example payload - publishing a non-live environment
Example payload - publishing a non-live environment
organization.project.environment.merged
Sent when one environment is merged into another. sourceProjectEnvironmentRemoved indicates whether the source environment was deleted as part of the merge.
Example organization.project.environment.merged payload
Example organization.project.environment.merged payload
organization.project.environment.deleted
Sent when an environment is deleted from a project.
Example organization.project.environment.deleted payload
Example organization.project.environment.deleted payload
Verifying requests come from Voiceflow
Once you enter a webhook URL into the settings page, you’ll automatically be provided with a webhook secret. This can be used to verify that events received by the webhook were really sent by Voiceflow. Follow these instructions to learn how to verify events using the webhook secret.
If you accidentally leak your webhook secret, you can regenerate it using the 🔄 button on the settings page. Note that your previous webhook secret will remain valid for 24 hours after you regenerate it.
If you’re receiving data from behind a restrictive firewall, you should know that events will come from one of Svix’s IP addresses, rather than Voiceflow’s.