Use HTTP Webhook as a trigger

If you encounter a scenario where Keragon does not directly support a trigger from a specific app, you're not out of options. Keragon offers a flexible alternative through its HTTP Webhook trigger.

HTTP Webhook

Follow the steps bellow to add the HTTP Webhook trigger.

1. In the workflow editor, click the "+ Add a trigger" button.

2. In the drawer that opens, search for HTTP and select it.

3. From the list of the available triggering events, select the Http / Webhook.

4. Click "Save"

5. Click the newly added "Http / Webhook".

6. Click the "Copy Trigger URL".

7. Publish the workflow.

8. Go to the vendor's dashboard and add this url in their webhooks section.

Receive webhook data in Keragon 

After completing the steps above and sending a test event from your vendor, you can view the incoming data in Keragon.

1. Click the checkmark icon in the upper right corner of your workflow, or visit your runs page.
2. Expand the HTTP Webhook step and click on the outputs tab to see the data from your webhook.

Map webhook data to steps

Once your webhook data is received in Keragon, you can map this data to any subsequent steps in your workflow using the variable selector.

1. Click on the workflow step where you want your webhook data to be passed.
2. Click on a specific input.
3. From the variable selector, select the data to fill this input.

Be aware that not every app supports webhook functionality. Before using Keragon's HTTP Webhook trigger for integrating unsupported apps, ensure to confirm webhook availability. This can typically be done by checking the app's documentation or by directly contacting their support team or your account manager.