- 1 Minute to read
- Print
- DarkLight
API Methods for Event-Based Automations
- 1 Minute to read
- Print
- DarkLight
Certain API methods can be used to trigger an event-based automation. In this case the API call is the event.
For more information, see Event-Based Automation.
API 2.0 and Control XML Methods
The following table lists the API 2.0 and Control XML methods that trigger an automation event.
Method | Event | Notes |
---|---|---|
groupClone | ||
All methods listed here plus userCreate | ||
messageSendSingle or messageSendTransactional | ||
userUpdateProfile, userReplaceProfile, userReplaceProfile, userReplaceProfileByEmail | The following API methods do not fire this automation: membershipUpdateAttributes | |
membershipCreate | The following API methods do not fire this automation: messageSendSingle or messageSendTransactional | |
membershipSubscribe, membershipSubscribeByEmail | Note that the automation does not fire if the contact is already a member of the group. This is true for all subscription modes. With the subscription mode DOUBLE_OPT_IN, the event executes with the API call, but Engage doesn't fire the actual job until the subscription is confirmed. The following API methods do not fire this automation: messageSendSingle or messageSendTransactional. | |
membershipUnsubscribe, membershipUnsubscribeByEmail | The following API methods do not fire this automation: membershipDelete | |
relatedDataDeleteRecord | ||
relatedDataCreateRecord | The automation will not fire if the dataset is linked to the user profile via email / mobile / fax. | |
relatedDataCreateRecord | The automation will only fire if the dataset is linked to user profile via email / mobile / fax. The automation will not fire if the dataset is linked with anything other than the email / mobile / fax. | |
All of the methods listed above can be used as the "login" event. | When defining the event, the field User should be the designated API user. Otherwise the event will fire on every user login in the user interface. |
API 1.0 Methods (REST only)
The following automation can only be triggered with the following API 1.0 method.
Method | Event | Notes |
---|---|---|
UpdateRecipientNoMsg with the parameter Self=True UpdateRecipientMsg with the parameter Self=True | The following API methods do not fire this automation: userCreate |