Table of compatibility between events and trigger actions Triggers impose some restrictions on what actions can be performed after certain events. This article contains a table of compatibility between events and actions to be performed. false W3sidGl0bGUiOiJBdXRvbWF0aW9uIiwidXJsIjoiL3VzZXJzL2F1dG9tYXRpb24tdXNlci8ifSx7InRpdGxlIjoiVHJpZ2dlcnMiLCJ1cmwiOiIvdXNlcnMvYXV0b21hdGlvbi11c2VyL2Z1bmN0aW9uLXRyaWdnZXJzLyJ9XQ== Automation /users/automation-user/ ["users","Automation"] ["users","Automation","Triggers"] users

Table of compatibility between events and trigger actions

Triggers impose some restrictions on what actions can be performed after certain events. This article contains a table of compatibility between events and actions to be performed.

Triggers impose some restrictions on what actions can be performed after certain events. This article contains a table of compatibility between events and actions to be performed.

|Event|Action| | : ———————————————- | : ————————————————- — | | Change of order | Send email by template
Send SMS by template
Change manager data
Change customer data
Change order data
Set a task
Send notification by template
Execute HTTP request
Call to customer
Add expense | | Change of customer information | Set a task
Send notification by template
Send an email by template
Send an SMS by template
Change customer data
Execute HTTP request
Call to a customer | | Missed call | Send email by template
Send SMS by template
Set task
Send notification by template
Execute HTTP request
Create customer
Create order | | New call | Send email by template
Send SMS by template
Set task
Send notification by template
Execute HTTP request
Create customer
Create order | | Customer visited the site | Send email by template
Send SMS by template
Execute HTTP request
Change customer data
Send notification by template
Set task
Call to customer | | Customer leaves the site | Send email by template
Send SMS by template
Execute HTTP request
Change customer data
Send notification by template
Set task
Call to customer | | Customer did not visit the site | Send email by template
Send SMS by template
Execute HTTP request
Change customer data
Send notification by template
Set task
Call to customer | | After a trigger is executed for a customer | Send email by template
Send SMS by template
Change customer data
Set task
Send notification by template
Execute HTTP request
Call to customer | | After trigger is executed for an order | Sending an email for order
Sending an SMS for order
Change manager data
Change customer data
Change order data
Set task
Send notification by template
Execute HTTP request
Call to customer |

Note

The events “Customer visited the site”, “Customer leaves the site” and “Customer did not visit the site” are available only if Collector is enabled.

When creating a trigger and then notifying the customer via SMS or email, it is important to remember that the events of the actions should correspond to the events in the trigger.

For example, for a trigger linked to the “Change of order” event, you need to have created a corresponding email or SMS beforehand.

Thank you for your feedback.
Was this article helpful?
No
  • The recommendations did not help
  • There is no answer to my question
  • The text is difficult to understand
  • I do not like the described functionality
Yes
Previous article
How to view the results of trigger executions
The results of trigger executions are recorded in the "Action log" section.