What is it?
We’ve made some exciting updates to the webhook action in Workflows:
- You can make GET requests to receive certain data from other tools and services
- You can use data from the webhook response in the rest of your workflow
- You can test your webhook action to ensure all is working correctly before taking it live
The webhook workflow action is available in Operations Hub Professional and Enterprise.
Find more information in this knowledge base article.
Why does it matter?
Webhooks in workflows enable HubSpot users to send information to external apps, automatically.
Up to now, they’ve had a glaring limitation: They’ve only enabled POST requests, so data only flows out of HubSpot (not into HubSpot).
With today’s updates, the Webhook action now supports GET requests — enabling both the sending and receiving of information — and makes it easy to use data from the webhook response to power additional automation.
Three examples, to get your creative juices flowing:
- Request data from your business intelligence tool, and use it to update your CRM.
- Pull zipcodes from public APIs to power your territory management.
- Create a scheduled trigger to automate weekly data enrichment or a nightly data warehouse dump.
The “GET” request makes it easier to connect all your data in HubSpot, and to streamline business processes and customer engagements using that data.
How does it work?
- Within a workflow, select the “Send Webhook Request” action - which has been renamed from “Trigger a Webhook”.
- Select what type of Webhook Request you want to send - a GET or a POST request
- Enter the Webhook URL you’re making your request to as well as if there is an authentication method
- Test your webhook by selecting the object you’d like to test with. We will then make a request to the url you provided above. You’ll then be able to see the status of the request as well as both the request HubSpot sent, and the response we received from the other service. If there were any issues, you’ll see error messages.
- Once you’ve tested your webhook, you can select the keys in the response tab that you can use in the rest of your workflow. You may select up to 20 outputs.
- Once you’ve selected your outputs, you will then see data from the webhook available as inputs in subsequent actions. If you do not test your webhook, you won’t see that data as an option to use later on in your workflow.