Adding Webhooks to your project

Webhooks are automated messages sent from one system to another when a specific event happens. They let different apps or services talk to each other in real time — instantly notifying your system when something important occurs, like a new form submission, or a status change.

Coreo provides two types of webhooks: one specifically for the Slack platform, and a more general webhook that you can use with your preferred web application, such as a CRM or an automation tool like Zapier.

How to set up a webhook

You can find webhooks under the Project Settings menu:

where you will find the Hooks tool:

This lists any webhooks you have already added, and a button to create new webhooks.

If you select ‘Create Hook’ you can then choose whether to create a Slack webhook, or a standard webhook:

In both cases the setup is the the same: select the action, add the target URL provided by your target system, and select the options you wish to send as part of your hook.

For Action: this is the main difference between Slack and other webhooks. For Slack, select ‘Post Message’:

and for other webhooks, select ‘Post data’:

Target URL: is the URL provided by your target system. For more information on how to set up Slack to receive Webhooks, see: https://api.slack.com/messaging/webhooks. For other systems check their support documentation on how to receive webhooks.

Under Surveys select the form from those available in the current project that you want to use to trigger your webhook.

Events allows you to select from a number of predefined actions which will provide data via your webhook:

  • Before Record Create, and Before Record Update: provide hooks that send the record data before it goes to Coreo. If your hook then returns a non-success message, the record won’t submit. This allows you to add custom validation, or similar checks before committing your records to Coreo.
  • Record Created and Record Updated: Coreo sends webhooks with the record data after it successfully creates or updates a record. These hooks can be used to trigger actions such as sending an email when a new record is created, pushing a message to Slack when a record is updated, or adding data to a separate spreadsheet.
  • Record Unsafe Image Detected: Coreo pushes all images uploaded via the Google Cloud Vision API service which anonymously checks images for potential harmful or unsafe images. This hook detects such images and returns warnings, allowing you to take any necessary action on the containing record.
  • User Joined Project: provides the details of a new user who has signed up to your project.

In Settings:

  • Allow Submit on Hook Failure: the record will be submitted even if the webhook fails – for example, due to a temporary service outage – when this option is toggled on.

When you have you have configured your webhook, press ‘Create‘ and your webhook will be ready to use.

You can edit your webhook with the pencil icon, or delete it with the bin icon:

Was this article helpful?

Thanks for your feedback!