skip to Main Content

Automator Pro 3.4: New Triggers & Features

Our penultimate Uncanny Automator Pro release of 2021 adds a number of new triggers to complete recent releases of the free version, as well as some support that will assist developers in particular.

Additional Divi Form support

The Uncanny Automator 3.5 release introduced support for Divi forms, and in Pro we’re rounding out the offering with 2 new triggers:

  • A user submits a form with a value in a field (for Logged in recipes)
  • A form is submitted with a value in a field (for Everyone recipes)

Divi Pro trigger for Automator

The new triggers will allow recipes to be invoked  via specific values in form submissions. Typical use cases might include enrolling a user in a course if their email address matches a certain domain, adding users to social or learning groups if a selection in a form matches a value, etc.

New triggers

Several integrations get new triggers in the Uncanny Automator Pro 3.4 release. Here’s a list of what’s been added:

  • WordPress Core: A specific role is removed from the user. This works just like our “A specific role is added” trigger, just in the reverse. Perhaps when a role is removed then a users CRM tags are updated or a membership level is removed.
  • LifterLMS: A user is unenrolled from a course. Perhaps when a user is removed from a course they’re also removed from a social group.
  • WooCommerce: A user reviews a product with a rating greater than, less than or equal to an amount. Product reviews can now trigger recipes, so perhaps when a review is left the user is presented with an offer or a notification is posted to a Slack workspace; it might even be automatically tweeted.

Other Enhancements

Automator Pro 3.4 includes several improvements, including the following:

  • MyCred gains support for decimal values. MyCred has always supported, but Automator previously required integer values in triggers. Decimals can now be used as well.
  • The WooCommerce everyone trigger for “a product is purchased in an order” was changed to “a product has its associated order completed, paid for or a thank you page visited”. Effectively we’re expanding the scope of the trigger because several users had issues related to when it would fire for guest checkout purchases. For any sites where this trigger is already in use, it will work exactly the same way and we’ll use the “completed” status of the order as the trigger.
  • Elementor Forms now have support for checkboxes and radio buttons for the “A user submits a form with a specific value in a specific field” trigger. This will make it much easier to run recipes based on selections rather than text values.

On a related note, we are quickly closing in on year-end. We do have one more big release planned, so keep an eye out for an announcement within the next 2 weeks!

This Post Has 0 Comments

Leave a Reply

Your email address will not be published.

Back To Top