Webhooks capture and orchestrate flows within FreeAgent based on real-time events generated by 3rd party systems having support for HTTP callback notifications - no more polling for changes on external systems which support callbacks.
Webhooks allow you to easily define new incoming HTTP webhooks to capture external integration-related events within FreeAgent as they happen.
Both GET/Post requests are supported.
User Permissions: Only Admins or App Admins can add new webhooks.
In this tutorial, we will cover the following topics:
Navigate to Webhooks
Go to Admin Settings > App Setup, there click your App's Name to display the available options, and click on 'Webhooks'.
Note: If you are now on Hazel, go to Admin Settings > Integrations > Webhooks.
Create New Webhook
Click the 'Create New Webhook' button. You will need to give your Webhook a name and add a description. We recommend that name is something easy to identify.
The URL field is greyed out, as it is a system field. This means that FreeAgent will automatically create a URL for your webhook.
Up next, there is the App field. If you got to the Webhook settings page through your App it will be already specified here. If you are an admin, you can choose between your existing Apps.
There are two supported methods for Webhooks:
| METHOD | DESCRIPTION |
| GET | Requests Data. |
| POST | Sends Data. |
If you are using your Webhook in an Automation, then you will need to select it in the Automation field.
Webhook for Automations
You can consume your wehbook as triggers for your automations.
It is important that you create the automation first and then your Webhook as there is a field in which you will have to specify the automation.
The alternative would be to create the Webhook first, then the automation and once it is done, you will need to update your Webhook to add the automation you just created.
Webhooks in Workflows
You can use Webhooks in Workflows to add support for 'Message Received' Events within them. This will allow you to pause/continue workflows through webhook-based triggers.