Webhook workflows
Explore webhook workflows and how to configure them.
Sending and receiving data represent a webhook. Use webhook workflows to capture events happening in your tools. When an event happens in your tool, your system can send this data to a URL generated by a workflow in Actioner.
To capture events happening in your Slack workspace, add a Slack workflow instead. Slack workflow is a specific type of event listener tailored for Slack. It is triggered with a set of events happening in your Slack workspace, such as new members joining a channel or new messages posted to a channel or reactions added to specific messages.
Similarly, to capture events happening in your HubSpot account, add HubSpot workflow. HubSpot workflow is a specific type of event listener tailored for HubSpot. It is triggered with a set of events happening in your HubSpot account, such as deal updates, new contacts being added to your CRM, or companies removed from your HubSpot account.
Let's take a closer look of the steps to build a webhook workflow.
Step 1. Add a new workflow
Navigate to your app in My apps page and go to Workflows tab and click + Add workflow.
Next, enter a name, description and tags for your workflow and select Webhook in type field.
Actioner generates a unique URL, towards which you can configure your system to send data. Copy the generated URL that looks like below:
https://api.actioner.com/v1/events?api_key=e61e1973-e785-471f-a235-ac22d5d15fd4
Configuration in your tool or service
Open the tool or service you want to send data to Actioner, and find its webhooks settings. You'll often find it in your tool's core settings or options page. If you’re unable to locate it, check your tool's help and support documentation.
In your tool's webhook settings, you'll typically choose to add a new webhook connection. Depending on the feature set your tool provides, webhook connections can be added by creating a new integration, alarm, notification, alert or a trigger, etc.
Paste the webhook URL you copied from Actioner, select any option your tool offers—including which data you want to capture with the Actioner webhook—and save your changes.
Make sure that POST method is selected and content-type is set as JSON — or data is sent with Content-Type: application/json Header.
You can filter the data that will be sent to Actioner, if your tool allows configuring a webhook for certain objects, records, entities or adding specific conditions.
Step 2. Test webhook or Add an example payload
Test webhook
Send data to Actioner
The tool that's sending events to the Actioner webhook URL will send data to it whenever something new is added (or updated, depending on your configuration).
To test a webhook trigger, you can first check if your tool is capable of triggering test data. If not, add something new in your tool. For example, if you're sending data from a ticking system such as Zendesk, you could create a new test ticket.
After sending data to Actioner, click Test webhook button to see the incoming payload in JSON format.
Add an example payload
Alternative to triggering test data, you can Add an example payload in JSON format. This will help you setup filters and action parameters in the next steps.
Step 3. Setup root conditions
Root conditions are used to evaluate data to decide whether or not to execute the steps. If conditions are met, Actioner executes the steps added to a workflow and ends the processing. If conditions are not satisfied, nothing happens.
To add a new condition, click + Add condition button.
To remove a filter click X right near it.
Your changes are applied after you save your changes.
→ Learn how to setup root conditions with dynamic data.
Step 4. Add your first step
Steps are the actions that are automatically run as a result of an event that triggers a workflow.
In a workflow, you can setup steps to perform an action in Slack, such as to post a new messages or to perform an action in your tool, such as to update a deal.
You can add one action to each step of a workflow. By adding multiple steps, you can set a workflow to run multiple actions in a sequence.
Click + Add step button to create a new step in your workflow.
You can add as many steps as you want. Multiple actions can run through a workflow
- if root conditions are satisfied AND
- if multiple step conditions are satisfied AND
- if actions added to steps (that has conditions satisfied) are run successfully.
The steps are run in top down order.
Step 5. Add step conditions
You can add additional conditions to your steps. The step is executed as long as
- Root conditions are satisfied AND
- Step conditions are satisfied.
Once the root conditions of a workflow is satisfied, workflow starts processing the steps in top down order. To decide whether to run a step or not, data is also checked against the conditions of that step.
If step filters are satisfied, Actioner executes the selected action and proceeds to next step. If conditions are not satisfied, Actioner does not execute the selected step. But processing does not stop.
Processing stops when an action added to an earlier step could not be successfully run or when the last step of the workflow is evaluated.
→ Learn how to setup step conditions with dynamic data.
Step 7. Select the step action and enter action parameters.
Select an action from your app that will be run once the step conditions are satisfied. When you select an action, the action's input fields open up. Provide parameters that the action will run with.
→ Learn how to configure your action parameters with dynamic data.
Step 8. Add new steps (optional).
If you are looking to run multiple actions through a workflow, you can add more steps.
You can add as many steps as you want. Multiple actions can run through a workflow
- if root conditions are satisfied AND
- if multiple step conditions are satisfied AND
- if actions added to steps (that has conditions satisfied) are run successfully.
The steps are run in top down order.