Pro 4.1: GravityKit Support, over 20 triggers & actions

Coming up with titles for posts about Uncanny Automator updates is hard, because there’s simply so much to include that a few words of text can’t possibly do the releases justice. Yesterday we released Uncanny Automator 4.1, which included 3 new integrations, a new editor, and tons of new triggers and actions. If you can believe it, today’s release of Uncanny Automator Pro 4.1 adds even more triggers and actions to the #1 no-code automation tool for WordPress.

We’re excited to introduce an integration for one new WordPress plugin, over 20 new triggers and actions, several new conditions and tokens, as well as support for basic authentication for incoming webhooks.

New integration: GravityKit

GravityKit (formerly GravityView) is an add-on for Gravity Forms that makes it easy to build things with data from form submissions. You can create tables, data-rich user profiles, directories, tables, maps, charts and more with this powerful WordPress plugin.

In the Automator Pro 4.1 release, we’re introducing these new triggers:

• An entry for a specific form is approved
• An entry for a specific form is rejected

Most of the related use cases will be around notifications and follow-up workflows, but we’re sure users will find many creative ways to use the new triggers.

Autonami overload

Yesterday’s 4.1 release added the new Autonami integration, and the 7 triggers and actions we added were pretty fantastic. But why settle for 7 triggers and actions when you could have 16? Here’s what the Pro 4.1 release adds to the integration:

• New trigger: A tag is removed from a contact
• New trigger: A tag is removed from a user
• New trigger: A user is removed from a list
• New action: Add a contact to a list
• New action: Remove a contact from a list
• New action: Remove the user from a list
• New action: Add the user to a list
• New action: Remove a tag from a contact
• New action: Remove a tag from the user

And with those changes, now we have a very rich integration with Autonami.

LearnDash

LearnDash users are going to really like the new actions and conditions in Pro 4.1. Let’s start with the new actions:

• Remove the user from all groups
• Unenroll the user from all courses
• Remove the user as a leader of a group

The first 2 actions will save a huge amount of time with cleanup. Instead of requiring actions for every course or group, if you need to remove a user from everything in bulk, a single action can now take care of it.

The third action is more interesting for new use cases. We added it based on the request to allow customers to subscribe to groups as Group Leaders, so we needed a way to remove that access if a subscription is cancelled or expires.

As for conditions, here’s what’s new:

• The user is a member of a group or its child groups
• The user is not a member of a group or its child groups
• The user has not completed a course

The first 2 open up a lot of opportunities for WordPress sites that are leveraging LearnDash Group hierarchies. Now, instead of defining conditions based on potentially a lot of groups, you can set conditional checks at the top-level parent for the group hierarchy.

The third condition is great for checking up on user progress and running workflows based on performance. Maybe when a user enrolls in a course, there’s an action to send the user a reminder in 30 days and notify their Group Leader if they haven’t yet completed the course. Yes, Automator keeps making it easier and easier to replace common CRM workflows for elearning sites.

So much Amelia

We went a bit overboard with additional Amelia support in this release too. Here’s what we’re adding in Automator Pro 4.1:

• New trigger: A booking of an appointment for a service has been changed to a specific status
• New trigger: A user’s booking of an appointment for a service has been changed to a specific status
• New trigger: A booking of an appointment for a service is cancelled
• New trigger: A booking of an appointment for a service is rescheduled
• New trigger: A user’s booking of an appointment for a service is cancelled
• New trigger A user’s booking of an appointment for a service is rescheduled

Yes, many of those sound similar, where the difference between several triggers is Logged In vs. Everyone recipe usage. Typical use cases here might include creating reports in Google Sheets, tagging and untagging contacts in a CRM, managing course enrollments, etc.

Basic authentication for incoming webhooks

In our quest to make Uncanny Automator the #1 tool for incoming and outgoing webhook support for WordPress, today we’re adding a new feature for authenticating incoming webhook traffic. Here’s an example of what the security header option looks like:

The screenshot above shows a sample with authentication using a username and encoded password. Certainly this webhook authentication support is intended for advanced users, but provides a more secure way for Automator to validate incoming webhook traffic with security headers.

And the rest

Uncanny Automator Pro 4.1 adds several additional triggers, actions and features.

The new HTML template features have now been added to the LearnDash “Send a certificate” and “Send an email to the user’s Group Leaders” actions; the Woo “Generate and email a coupon code to the user” also gets the new support. This means you can use full HTML templates in your email bodies and the code will not be modified by TinyMCE or the WordPress editor, it will stay intact.

BuddyBoss gains a new action to create friendships between any 2 users. Users can be mapped directly in the recipe or, as always, custom user IDs can be passed in.

To make data cleanup easier, there’s a new WordPress action to move all of a specific type of post with a taxonomy term in a taxonomy to the trash. In simpler terms, you can move all posts meeting certain criteria to the trash, like maybe all products with a certain matching category. WordPress also gains 1 new trigger: A taxonomy term is added to a specific type of post. So maybe if a blog post is added to the “Share” category, it’s shared on social media, or maybe a course that has a “public” tag added triggers a Mailchimp campaign and has a “Featured” category added so it’s moved to the top of a course grid for improved promotion.

In our LifterLMS integration, the “Remove the user from a membership” action gets an “All memberships” option. And in Groudhogg, Tag ID and Tag Name tokens are now available for the triggers.

Last, but certainly very far from least, the Automator Action Logs get a new filter that allows displaying a list of records based on status. This makes it a lot easier to pull up a list of Scheduled actions only, Skipped actions, actions that experienced some type of error, etc.

For the full list of updates, make sure to check out the changelog.