Use webhook triggers

What is a webhook trigger?

Webhook triggers are an effective way to kick off a workflow with context from external systems. By sending an API request to a webhook trigger, Rewst will fire the workflow and include any data and or queries included in the request. For example, when a customer submits a support ticket, a webhook instantly sends that information to Rewst and starts a workflow.

When using webhook triggers, design your workflow with our rate limiting policy in mind.

Webhook trigger process

Webhooks follow a simple process:

1. An event happens, such as when a new ticket is submitted.

2. The webhook sends a message with data to a URL.

3. A workflow is triggered based on that message.

Webhook URLs

A webhook URL is a unique address where data is received for that particular webhook. It continuously listens for data, and kicks off the related workflow the moment data is received. Once that data is captured, we call it a payload, and it becomes usable inside the workflow. This allows you to do things like:

• Assign tasks based on field values

• Push updates to other systems

• Send messages or alerts

• Store or log information for reporting

Webhook URLs are formatted consistently using the trigger ID and organization ID. The format is as follows: https://engine.rewst.io/webhooks/custom/trigger/{{ Trigger ID }}/{{ Organization ID }} . Find the webhook URL in the Details tab of the trigger node after it's been placed on the Workflow Builder Canvas.