Automation Trigger Based Condition Attributes and Mail Merge Tags

When crafting intricate automation workflows or implementing precise wait conditions, you can harness the power of attributes derived from the specific trigger that initiated the client's entry into the automation.

For example:

• Trigger: "Purchased a Package"

  If your automation is triggered by a package purchase, you can employ advanced conditions that leverage attributes associated with that particular package. These attributes might include:

  • Expiration Date: Set up conditions based on the package's expiration date, such as sending reminders or taking specific actions as the expiration date approaches.
  • Remaining Credits: Implement conditions that depend on the number of credits left in the package, like triggering actions when a certain threshold is reached.
  • Package Title: Tailor your automations to different package types by using the package title as a condition.
  • Package Active Status: Determine whether to proceed with automation steps based on the package's active or inactive status.

Furthermore, when sending emails:

You can dynamically incorporate relevant package attributes into your email content to provide personalized and informative messages. These attributes could include:

• Package Title: Clearly identify the purchased package in the email subject and body.
• Remaining Credits: Display the current number of credits available to the client.
• Expiration Date: Provide a clear reminder of the package's expiration date.

By effectively utilizing these trigger attributes, you can create highly targeted and efficient automations that enhance the overall user experience.

The video below demonstrates these attributes:

You can see examples of how these are used in the built-in automations that we provide for you:

• Built-In Automations - Package Expiration Reminder
• Built-In Automations - Package Credits Running Low
• Built-In Automations - Membership Renewal Reminder