Later on, you might be viewing many of your webhooks listed somewhere else and you may forget what they were for. The name can be anything that you want, but it's useful to make it descriptive so that it's clear what it's doing. The Webhook initially requires two values. We'll add a new webhook action to the end of this. In our Field Sales app, we have a custom action set up to trigger after an order is approved. It will not work with Public apps without sign-in. If you're non-technical, one of the easiest ways to get started with Webhooks is to use a workflow automation tool like Zapier or Integromat.įor security reasons, webhooks will only work when a user is logged into an app.

If you're an experienced developer, you can read Mark's post on the forum detailing the use of Webhooks. Just using the Webhook Action alone does not allow you to talk to any service – you need to configure the endpoint (receiver) correctly.

Webhooks can be used in lots of different ways but do require a specific format – and technical knowledge to implement. To demonstrate how to configure a webhook, we'll set up the third scenario – sending sales info from a Field Sales app to our accounting software.

After a new sale is processed, send the details of that order to your accounting software.

When a user submits a form, take the attached images, convert them to files and upload them to dropbox.

When a user clicks a button send the details of the current item as an email.

The use-cases for this are limitless but here are a few examples to give you the idea. Glide's Webhook Action lets you send data from your app to another app. For example when a new payment is made in Stripe, send that data to Slack as a notification. Webhooks let these programs speak to each other and to be notified when something happens. Here, we mean apps in the broadest sense – Gmail, Facebook, PayPal, Slack. Webhooks are a way for apps to send messages to other apps.

Webhooks slack