Webhook triggers
Explore webhook triggers and how to configure them.
What are webhook triggers?
Webhook triggers enable the execution of workflows in response to HTTP requests received from external systems or applications. A webhook trigger acts as an entry point for initiating a workflow based on events or notifications sent by external sources.
When a webhook trigger is set up, Actioner generates a unique URL that can be used as an endpoint to receive incoming HTTP requests. These requests typically contain data or information related to a specific event or update from your external system.
Webhook triggers provide a flexible and powerful way to integrate with external services and systems. They allow you to capture real-time events or updates from various sources and trigger the corresponding workflow to process the received data.
Some key features and benefits of webhook triggers in Actioner include:
Real-time event processing: Webhook triggers enable instant response to events or notifications from external systems, ensuring timely processing and action within your workflows.
Event-driven automation: By setting up a webhook trigger, you can automate specific actions or processes based on the occurrence of specific events or updates from external sources.
Versatile integration: Webhook triggers can be integrated with a wide range of applications, services, or platforms that support sending HTTP requests, allowing you to connect and interact with external systems seamlessly.
Customizable payload handling: Actioner allows you to define how the incoming payload from the webhook request is processed within your workflows. You can extract relevant data, perform transformations, or trigger specific actions based on the received information.
Security and authentication: Actioner provides options to secure the webhook endpoints. This ensures that only authorized requests are accepted, enhancing the overall security of your integrations.
With webhook triggers, you can create dynamic and event-driven workflows that respond to external events or updates in real-time. This capability enables you to automate processes, synchronize data, and streamline communication between different systems or applications.
How to create workflows with a webhook trigger
Step 1. Create a workflow
To create a new workflow and open your workflow in canvas mode:
Navigate to your app's Wokflows tab and create a new workflow.
Give your workflow a name, provide a description and add tags optionally.
Step 2. Create your trigger
- Select Webhook from trigger options.
On the opening panel, you can give a new name to your trigger.
Actioner generates a unique URL, towards which you can configure your system to send data. The generated URL looks like below:
https://api.actioner.com/v2/events?api_key=e61e1973-e785-471f-a235-ac22d5d15fd4
*The API key at the end of the URL is generated as a unique key each time you add a new webhook trigger.
Step 3. Configuration in your tool or service
Go to 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 asJSON
— or data is sent withContent-Type: application/json
Header.
Step 4. Test your trigger
Your tool that's sending events to the Actioner via a webhhok will send data to it whenever something new is added (or updated, depending on your configuration).
To test your trigger, you can first check if your tool is capable of triggering test data. If not, add something new in your tool. if you're sending data from a issue management tool such as Jira, you could create a new test issue.
Click Test webhook to use that data while designing your workflow.
Step 5. Configure your trigger's conditions
- Configure your triggers's conditions.
Step 6. Add your action(s)
Add a new node. Select Actions option and then select your integration from the opening list.
Select your action from the actions list and configure your action's parameters to run the workflow.
→ Learn how to use actions in your workflows.
Step 7. Save your workflow
- Once all is set, apply changes to your workflow.