Rules are used to group filters and actions together. You can set multiple rules for a webhook link, but at least one rule is required.
Incoming data undergoes evaluation against every rule's filter conditions. If a match is found, the corresponding actions associated with that rule are executed.
Each rule is like a mini-instruction set. It consists of several key parts:
Name | Description |
---|---|
Name | A brief internal description of the rule. |
Status | You can pause each rule individually. Pausing a rule temporarily prevents it from evaluating filters or executing actions. This is useful for keeping the rule without deletion. |
Filters | Filters allow you to validate and filter incoming requests. Filters are optional. Read more about filters. |
Actions | Once a request passes through the filters, predefined actions are executed. Use actions to email one or more recipients with the data from the incoming request. At least one action is required for each rule. Read more about actions. |
Leaving filters empty will cause every request to trigger the actions. This means any data, regardless of its content, will be processed according to the defined actions.
In the schema below, you can see an example of a webhook link with two rules.
"Rule 1" has two filters that check if the payment.status
is 'paid'
and if the
payment.amount
is greater or equal to
100
.
If the data passes the filters, actions will be executed.
It'll send one email to John and one email to Lisa.
"Rule 2" has two filters that checks if the payment.status
is 'paid'
and if the
product.id
is 123
.
If the data passes the filter, a single action will be executed, and it'll send one email to Maria.