Articles on: App Integrator

Trigger types and components

An entity that responds to a configured event in the application by launching the automation and passing the data that came in the event. For example, a trigger can respond to the creation or modification (tracking of the "modified date" parameter) of an entity in the application. Each trigger has its own "internal filter", which indicates that it needs to be launched, that if certain attributes are equal to the selected value, for example, a certain type of event comes with a webhook, or the API trigger makes a request for a specific URL to get a specific entity.

Trigger types

There are two models of trigger behavior, the model is selected at creation:

Webhook: A trigger responds when an HTTP request arrives at the webhook URL (created and attached to the connection). A filter is configured for each trigger, which indicates that a specific set of variables with the specified value should come in the request.

Outgoing API request: The trigger independently makes an HTTP request to the specified URL (to the application) every five minutes, from which it receives a list of entities and filters them according to the selected parameters (e.g., ID).

Trigger types can be combined, there are no restrictions.

Trigger components

A trigger has three main components:

Fields: Create trigger fields, which will store the values ​​received as a result of the event. Fields have their own names and types.

Webhook catcher: Attach a separate application entity, which allows you to catch dynamic data from the webhook, in the case when setting the mapping is impossible.

Requests: Set up the trigger request widgets, here it is indicated which variable from the request should be taken and in which trigger field to store its value at the event.

Data filtering: Indicate which trigger fields should be checked for each event, so as not to receive the same events, we attach a separate entity.

There are also two additional trigger components:

Line Sections/String: Allows you to create a section that receives data from an array of objects. Thus, if an array of an indefinite number of objects (e.g., Goods) comes along with the main entity, they will be transferred within the framework of one event.

Sorting: Allows using drag & drop to change the sorting of displaying fields in a bundle.

Updated on: 07/12/2022

Was this article helpful?

Share your feedback


Thank you!