Rules
Overview
If you prefer to receive notifications only when predefined criteria are met, you can set up rules when creating a orquestration webhook. The rules consist of three components: variable, operation, and value.
The available operations vary depending on the data type of the variable:
uuid
and string
EQUAL
, NOT_EQUAL
, IN
, NOT_IN
integer
EQUAL
, NOT_EQUAL
, IN
, NOT_IN
, LESS_THAN
, GREATER_THAN
date
and time
LESS_THAN
, GREATER_THAN
boolean
EQUAL
, NOT_EQUAL
Rules must be specified during the creation of a webhook, provided via the rules
attribute. Below is an example of a body with multiple rules for reference:
To discover the variables available for creating rules, refer to Metadata.
Examples
Below are groups of frequently used rules that can be included in your custom webhooks and combined with the webhook templates presented next.
Execution status
Success
Every successful execution that has encountered any data.
Failed
Every execution that results in a failure.
Dependent jobs
Filter only the main tables (endpoints with nested tables generate a separate webhook for each table when this rule is not used).
Time
Executions during weekdays between 00:00 BRT and 08:00 BRT.
Execution type
Filter only Full Refresh executions.
Schedules
Filter only scheduled executions.
Orchestration
Filter only executions triggered programmatically.
Last updated