Trigger Webhook
For security reasons, webhooks will only work when a user is logged into an app. They will not work with Public apps without sign-in.
Webhooks are a way for apps to send data to other apps. Here, we mean apps in the broadest sense—apps, products, services, and software like Gmail, Facebook, PayPal, and Slack.
Webhooks let these programs speak to each other and to be notified when something happens. For example; when a new payment is made in Stripe, send that data to Slack as a notification.
The Trigger Webhook action sends data from Glide to an external app. It can be used as an action in components (like Buttons, Collections, and much more), or it can be triggered along with other actions as part of a Workflow.
The use cases for the Trigger Webhook action are limitless. Some examples include:
- When a user clicks a button, send the details of the current item as an email
- When a user submits a form, take the attached images, convert them to files and upload them to dropbox
- After a new sale is processed, send the details of that order to your accounting software.
Understanding Webhooks
Webhooks can be used in lots of different ways but do require a specific format. Just using the Webhook action alone does not allow you to talk to any service—you need to configure the endpoint correctly.
Read Mark’s post on the forum detailing the use of Webhooks.
Webhooks in Glide require two pieces of data: the webhook URL and the values to be sent. The webhook URL will come from whatever service you’re connecting to. If you’re connecting with Zapier or Make, you’ll need to first set up the webhook in those platforms, then add the URL to Glide.
The values can come from a variety of places in Glide. They can be:
- Special values such as the Current Date/Time and User’s Email
- Column values
- User profile values
- Custom values
Setting up the Trigger Webhook Action
Layout Editor
Workflow Editor
Click on the plus (+) sign in the Components panel to add a new component that supports actions, or select an existing component to add an action.
Check the Introduction to Actions page for a full list of components that can be used to trigger actions.
Frequently Asked Questions
Do I need a paid plan for Trigger Webhook?
Yes, a paid plan is required to use Trigger Webhook. An earlier version of Trigger Webhook was available on free plans. Existing instances of this legacy action will continue to work for users who have set it up, but new instances cannot be created.
How does Trigger Webhook use updates?
Trigger Webhook will use one update every time it runs. Keep in mind that if your webhook adds, edits, or deletes multiple lines of data, it will use one update per line of data changed.