Articles on: App Integrator

Trigger data filter

Set up the field to track receiving data. If they duplicate the previous data, the trigger will not start the automation.

Such a scenario is useful for Webhook triggers. It allows you to track the entity or transaction ID, as well as protect from spam if the app sends several requests at once.

This scenario is also useful for API triggers, which send requests to the app every five minutes and receive duplicates.

The settings will allow you to remember the values ​​of the fields, within the history of one automation, so that the entity does not come into one automation several times.

Duplicate search in each request

Select one or several fields (string and integer field types are available). The trigger starts and saves the received value. In case of receiving the same entity, the trigger doesn’t start. For example, you can use the entity ID.

Track entity date

Select one field (the DateTime field type is available). The trigger starts and saves the value in the first field and the date in the date field (ed. Date of change). If the trigger receives the same entity (e.g. with the same ID), then the trigger will start only when the value in the date field differs.

Use this setting if you want the trigger to track “entity change”.

For a trigger with a date tracking setting, a checkmark “**Receive entity only once**” will appear in the settings. The rule of the checkbox is to stop the date tracking in the automation and save the field of the first checkbox.

Updated on: 07/12/2022

Was this article helpful?

Share your feedback


Thank you!