Webhook triggers

Use a Webhook trigger to start a workflow when an event occurs on a different platform (such as a customer response on a customer support ticket or a change to the application status in your applicant tracking system). You can also analyze the webhook response payload and extract useful variables that you can use in further steps of the workflow.

🚧

You can find the destination webhook URLs in the developer documentation of the third-party apps.

Watch a tutorial

Set up a webhook

1. Go to Workflows.
2. Click Create new ...> Start a new workflow.
3. Give the workflow a name and click Create.
4. Click the start section in the left-hand panel.
5. Select Webhook trigger.
6. Select to enable the webhook.
7. Copy the Next Matter URL from the webhook URL field.
8. Go to the third-party app and select the payload you want to send to Next Matter
9. In the third-party app, make a POST call to the copied Next Matter URL. This way we'll be able to receive the payload.
10. Go back to Next Matter and click Test webhook and select variables. This will fill in the response body with payload data, and populate the variables dropdown.

🚧

Tip: We recommend running the webhook test from time to time to make sure the payload is up to date. If the new payload doesn't return some of the variables that have been selected, these variables get highlighted and should be deleted so that they don't break the workflow.

11. Select the variables from the dropdown and click + Add for every variable you want to use later in the workflow. You can also add your own variables in the Active webhook variables section.
    If you plan to re-se these variables in further steps, the variables will display in the workflow metadata section as webhook variables.
12. Click Save.

Now, when an event happens, it triggers an instance and automatically populates the workflow data as per the selected variables.

Disable the webhook

If you don't need a webhook any more, you can disable it by clearing the Enable webhook box.

Note that this action deletes all data related to the webhook. If any workflows still use the variables extracted from the webhook's payload, these variables will show as broken and might cause the workflow to fail.