WordPress membership plugins can help you design user profile pages, restrict content and create unique…
Hot on the heels of the Uncanny Automator 4.2 release, we’re excited to introduce Uncanny Automator Pro 4.2, which adds a lot of new things: triggers, actions, tokens, conditions, and even a few behind-the-scenes improvements. There are almost 30 new triggers and actions alone. Let’s jump in to what’s new for Pro users.
The triggers we added for Fluent Support in our 4.1 release (when we introduced the integration) were a bit weak, so we’re making up for lost time. Here’s the full list of triggers that are in the Pro 4.2 release:
- A ticket for a product is closed by a customer or agent
- A ticket for a product is opened by a customer or agent
- A ticket for a product is replied to by a customer
- A ticket for a product is replied to by an agent
- A ticket with a specific priority is closed by a customer or agent
- A ticket with a specific priority is opened by a customer or agent
- A ticket with a specific priority is replied to by a customer
- A ticket with a specific priority is replied to by an agent
As you can see, if you want to trigger anything based off of some kind of ticket creation or update, Automator has you covered. There’s a single new action too, and it’s amazing: Create a support ticket.
Imagine the possibilities… when payment fails for an order, create a ticket automatically so the support team can follow up with the customer. Or maybe when a long-time subscription is cancelled, a ticket is created to reach out to the customer and try to win them back. You could even use it for system-related things, so when a recipe fails, you create a ticket that pre-populates the recipe information so someone can investigate why it fails.
We have some pretty great additions for sites that leverage LearnDash groups and have Group leaders. There are 2 new triggers available:
- A Group Leader is added to a group
- A Group Leader is removed from a group
Why? We built these ones to address a few scenarios we started to see creeping up on LearnDash sites. The primary use case we had in mind was to create alerts for groups with multiple Group Leaders–if there were a change in Group Leader/instructor staffing, other Group Leaders could be notified. So if a new Group Leader joined, or was removed, other Group Leaders would be kept in the loop. This could even be used to trigger exit interviews and surveys when a Group Leader leaves a group or organization.
Of course, to support the notification scenario above, we needed a new action:
- Send an email to Group Leaders of a group
We had other email actions to cover students inside a group, and some types of communication to Group Leaders, but this Group Leader email action makes more opportunities available.
There’s also one new token for LearnDash; when the “user submits an assignment” trigger is used in a recipe, the assignment URL is now available for the recipe actions.
- A user is approved for a membership level
- A user’s access to a membership level is cancelled
- A user’s access to a membership level is unapproved
- A user’s access to a membership level is uncancelled
- A user is confirmed for a membership level
- A user is unconfirmed for a membership level
These triggers are all pretty self-explanatory. Typical actions might include removing users from groups, revoking access to a course, restoring previous event enrollments, etc.
- New trigger: A payment fails for an order
- New trigger: A guest completes, pays for or lands on a thank you page for an order with a specific coupon
- New trigger: A product has its associated order set to a specific status
- New action: Set the user’s subscription to a specific variation of a variable subscription product to a status (this may set a record for longest action title?)
- New action: Set the user’s subscription of a subscription product to a status
Remember the example above for creating a support ticket when a payment fails? That first new trigger is how you can do it. And that second trigger is very exciting; you can run recipes based on the redemption of specific WooCommerce coupons.
There’s one new trigger for our BuddyBoss integration that comes from a customer request: “A user joins a hidden group”. Previously we could target public groups in recipes, but the user made a good case for supporting hidden groups specifically.
And then there’s a big new action: “Show an on-screen notification to the user”. This one is much like how we can pop up notifications in tools like OptinMonster and Elementor, just with BuddyBoss native notifications. So, any time you want to show a subtle onscreen message bubble to users as part of a recipe, Automator Pro can make it happen!
Automator and WordPress Core
We like to highlight the third party plugins first in release announcements, but the 2 additions to core functions are both huge additions.
On the WordPress core side, there’s one new action: “Add a comment to a post”. Use your favourite form tool as a way to submit comments to your site, push comments for an article on one site to the article on another site.
We added 2 new FluentCRM conditions to Uncanny Automator Pro 4.2:
- A user has a tag
- A user does not have a tag
These additions mean you can run specific actions based on whether or not a user has a specific tag. Perhaps if they have a “Gold” tag when they make a purchase, you add store credit to their account. Or if they don’t have a “Certificate” tag on course completion, you send them a congratulations email instead of a course certificate.
And the rest
In no particular order, Automator Pro 4.2 adds:
- Entry ID, User IP, Entry date and Entry source URL as tokens for Formidable Forms triggers
- Product category and Product tag tokens for “A product has its associated order completed, paid for, or a thank you page visited” in WooCommerce
- The WooCommerce “Create an order” action gets support for shipping method fields and additional token support
There’s more, of course, so make sure to check the changelog for full details.
What new additions are you most excited about? Let us know in the comments!