Trying to manage all of your WordPress automations can feel like trying to cook a…
Less than a month after the launch of Uncanny Automator 4.0, we’re back with another huge release. This free update to the most popular no-code automation plugin for WordPress packs in 3 new integrations, new features and a revamped post/email editor.
Let’s jump right in to what’s new in Uncanny Automator 4.1.
The #1 requested integration not already in Automator is here, and this initial release is packed full of useful triggers and actions—all free. For those not familiar with it, Autonami (by WooFunnels) is a marketing automation and CRM tool for WordPress. With an incredibly robust feature set, it’s growing quickly and maintaining perfect review scores on WordPress.org. Here’s what’s included in the Automator 4.1 release:
- New trigger: A contact is added to a list
- New trigger: A tag is added to a contact
- New trigger: A tag is added to a user
- New trigger: A user is added to a list
- New trigger: A user is set to a specific status
- New action: Add a tag to a contact
- New action: Add a tag to the user
We met up with Daman, the founder of Autonami, back in March. We couldn’t be more excited to introduce more people to Autonami and to allow current Autonami users to take automations to the next level. It’s a great product and the new integration opens up an incredible variety of new user cases.
And if you think this is exciting now, wait until you see what’s in Automator Pro 4.1.
While still relatively new to the market, Fluent Support has quickly developed a loyal following and is one of the best ways to offer Help Desk services directly from a WordPress site. Uncanny Automator 4.1 adds support for the following new triggers:
- A ticket is opened by a customer
- A ticket is closed by a customer
- A ticket receives a reply from a customer
There are, of course, many powerful use cases here that Fluent Support can’t otherwise offer, like sending a record of tickets to Google Sheets to build reports, tagging users in a CRM when a ticket is opened, notifying a user’s LearnDash Group Leaders that they’ve opened a ticket, etc.
Google Calendar (beta)
We’re excited to release another native, 1-click integration with a Google product, this time Google Calendar. This new option adds the following actions:
- Add an attendee to an event in a Google Calendar
- Add an event to a Google Calendar
- Remove an attendee from an event in a Google Calendar
This allows recipes like adding a user to an event when they make a purchase or enroll in an elearning course, removing them from a scheduled event if a CRM tag is removed, creating an event when a form is submitted, etc.
Just like with our original introduction of Google Sheets, we’re launching this integration with a “beta” label because the Automator app hasn’t yet been approved by Google. This means there will be a warning when you try to connect via our app and only the first 100 users to connect the integration can use it. Once Google sees some traffic via the app and early usage, the app should be approved quickly and it will move out of the beta phase.
To get started with Google Calendar, make sure to check out the Knowledge Base article first.
Email and post editor changes
Before we move to some of the other new triggers and actions for existing integrations, we want to highlight some huge changes we’re introducing in 4.1 to actions that send emails and create posts. We’ve had a lot of feedback that TinyMCE (the default post editor in WordPress and that we use for these actions) causes too many challenges when working with raw HTML. This makes it difficult to leverage external email templates and to preserve exact formatting in emails.
And here’s what you’ll see in Automator 4.1:
Besides the additional controls, this new editing tool fully preserves any HTML you use in the Text view. This means you can start reusing email templates, and in future, maybe we’ll introduce an email templating system to Automator.
One very important consideration with our new approach is that you can now add any code you want and the editor won’t clean it up for you, so if your code has issues, you can break the output. We’re confident the benefits of preserving HTML and code are worth it, but it’s an important consideration for novices.
Other triggers and actions
The descriptions below might be short, but make no mistake, these are incredibly powerful additions that will be immensely valuable on some Automator sites.
WordPress Core gains a new action to erase a user’s data (not delete an account) based on a privacy request. So if a user submits a form to request that their personal data be deleted as part of GDPR compliance, Automator can run the option built into WordPress to Erase Personal Data. We’re not doing anything unique on our side, simply executing the WordPress function to erase personal data as part of a recipe.
Uncanny Toolkit Pro for LearnDash users gain some important additions for our Simple Course Timer. There’s one new trigger: A user’s time in a course exceeds a specific number of minutes. As one example, this opens up a completely new opportunity for offering time trials of courses. In other words, you could have users sign up for a free account that gives them 30 minutes of course time. If they don’t purchase the full course, after the 30 minutes they’re redirected to a sales page any time they try to access course materials. There’s also one new action: Reset a user’s time in a course. Perhaps when users retake a course their existing time records are reset so they see the new total only.
Amelia users gain 2 new triggers:
- A guest registers for an event
- A user registers for an event
And GamiPress gets 1 new trigger: A user earns greater than, less than, equal to (etc.) a number of a specific type of points in a single transaction.
There’s a big new “common” token type for Pro users running multisite: “Current Site ID”. This token only shows up when multisite is active and it returns the get_current_blog_id() value. One interesting use case here might be using form submissions where a user is created on a specific network and assigned access to that site based on a value in a form field.
And the rest
Uncanny Automator 4.1 adds a few behind-the-scenes improvements as well. One useful addition is for webhook troubleshooting, so now if a sample is sent to another system and there’s an error, details of the error are returned. An example would be an invalid SSL certificate; instead of Automator just returning an error, now the error details from the other system will be visible. There’s similar messaging now for Instagram when an account limit is reached, so instead of showing a recipe as “Completed”, error details are available.
Google Sheets gains support for using worksheets in shared Google Drive.
The LifterLMS action to “Remove the user from a membership” gains an “All memberships” option to remove a user from everything.
And the Mailchimp action to “Add a tag to a user” now adds the user to the associated list if the user isn’t already a member.
Uncanny Automator 4.1 is undoubtedly huge, and to see a full list of updates, make sure to check out the changelog.
Stay tuned for the imminent Pro release. There’s a lot more coming for Autonami, LearnDash and Amelia users in particular… and perhaps another integration!