Subscription Workflow Default Behavior

Avatar

Avatar

jchapman-CC-82

Avatar

jchapman-CC-82

jchapman-CC-82

10-02-2021

Is there any documentation about the default behavior of a service subscription event setup? We are looking at an option to enrich the transactional email received by the end-user with profile data when they receive a subscribe or unsubscribe event. However, so far, that is not working and instead returns an error of anything attempting to be pulled from context.profile.

In attempting to set up our own workflow and/or event configuration, we cannot find anything that shows what the default behavior is for the subscription event to attempt to model after this at all. Is there a diagram or configuration setup hidden somewhere that we just cannot find in all of the documentation?

Accepted Solutions (1)

Accepted Solutions (1)

Answers (0)