Introduction to Webhooks in Glide

Your Glide system contains a wide and growing number of events that can trigger the instant publishing of information to webhooks. This includes a wide range of information about your clients, jobs, invoices and scheduler bookings.

There are a variety of popular 'Connector' applications such as  ZapierIFTTTMicrosoft Flow that can create and host a webhook for you. Typically these programs will allow you to configure mini programs (e.g. Zaps) that run instantly when information is published to the webhook, allowing you to instantly share your Glide data with other applications (e.g. when you create a bill in Glide then create a bill in Quickbooks or when you progress a job in Glide publish a message to Slack). When using the above applications they will provide the URL (web address) and you will paste this into Glide, in accordance with the notes below.

If you host your own web server then of course you can create your own webhooks and enter the web addresses into Glide.

Trigger events:

It is currently possible to trigger on these events:

  1. Via a workflow action, i.e. trigger when a job takes a workflow step, this includes:
    1. Job creation.
    2. Removal of job from the job pool.
    3. Any specific progress button being pressed.
  2. Literally any (i.e. all) progress button being pressed.
  3. Client creation.
  4. Change in client status (between active, prospect, lost, deleted).
  5. Creation of new resource booking on Scheduler.
  6. Edit resource booking on Scheduler.
  7. Delete resource booking on Scheduler.
  8. Creation of a new bill.

Setting up a new webhook trigger:

Depending upon which event you wish to trigger you will either configure this via the Configure Webhook Triggers page or in the Workflow Editor. Both of these are in the Config menu and only a superuser can configure them.

Configure workflow action triggers:

In the workflow editor you can set up a trigger that is triggered whenever a job takes a workflow step. Remember you will have a special workflow step that is taken when a job is created, optionally another special step that is taken when a job is removed from the job pool and a step for every progress button users press on job cards. This is events 1 in the list above.

  1. Click on the Config menu (remember you'll need to be a superuser to do this).
  2. Click on Edit workflow systems.
  3. Drill into the relevant workflow system by clicking on the pencil icon to the right of the name.
  4. Click on the workflow routes tab.
  5. Scroll down to the route that you wish to add the action to, find the appropriate workflow step (e.g. Sent to client etc) and click Create new action.
  6. Select the Send data to a webhook workflow action, paste the URL (e.g. from Zapier) and give the action a title. Click save.

This article gives a complete example of how to do this, the example shows how to share job information with Slack when a job is progressed using Zapier. The video at the bottom of this article covers the same demo.

Configure triggers on the Configure Webhook Triggers page:

On the Configure Webhook Triggers page you can add any number of Webhook URLs for Glide to publish data to on events 2 to 8 in the list above.

  1. Click on the Config menu (remember you'll need to be a superuser to do this).
  2. Click on Configure Webhook Triggers.
  3. Scroll down to the Glide event that you wish to trigger on.
  4. Click on the green + New button.
  5. Paste the URL (e.g. from Zapier) and click save.

Other information:

On the webhook trigger page you can see how many times information has been published to each webhook, you can see the exact data that was sent and you can delete the triggers. You can also see all of the same information for webhooks you are publishing to via workflow actions.

If you have more requests for webhook triggers please let us know via our  Feature UpVote page.

Slack via Zapier Example video:

Still need help? Contact Us Contact Us