At Uncanny Owl, our team works hard to understand what people are doing with Automator…
We’re excited to announce 2 new integrations in the Uncanny Automator 4.13 release, as well as several other important changes that will make some existing recipes a lot more useful. Let’s jump in to what’s new.
New integration: WPCode
WPCode is a plugin and platform that we have started using more ourselves to make our own snippets more accessible. (If you’re not familiar with our snippet library, it’s available on our development documentation site.) WPCode’s library of built-in snippets makes it easy to implement hidden and powerful functions for WordPress as well as popular plugins. Widely-used snippets include things like allowing SVG file upload, disabling the Gutenberg editor, disabling automatic updates, etc. You can also add your own code snippets to the plugin and control exactly how and when they’re loaded. And with today’s Automator release, it’s easier than ever to turn them on and off. Version 4.13 adds these 2 actions for WPCode:
- Activate a snippet
- Deactivate a snippet
Why would you want to enable or disable code snippets via recipe? Here are a few possible examples:
- Allow authorized users to enable or disable certain site features in the front end, without /wp-admin/ access, by checking and unchecking selections in a form that control site snippets.
- Run a sale, where banners and code related to the sale are managed via snippet, and set the snippet to be disabled automatically at the sale end time.
- Coordinating a promotion where users are directed to submit a form, but after the 100th submission activate a snippet that removes the promotion and hides the page.
New integration: Thrive Ovation
In case you’re not familiar with it, Thrive Ovation is a popular plugin developed by Thrive Themes that helps WordPress site owners collect, manage, and display testimonials on their websites. Our initial integration focuses on one of its many features: testimonial capture. With that in mind, Automator 4.13 adds one new trigger:
- A testimonial is submitted
This new trigger offers a ton of new tokens (e.g. description, role, website URL, email, status, etc.) so that you can use the testimonial data in a variety of ways. Maybe you use the new trigger to keep a lot of testimonial details in Airtable, post positive ones to Facebook (why not use our OpenAI integration for sentiment analysis to figure out which submissions are positive?), notify staff in Slack and tag the user in Groundhogg.
Other updates in 4.13
One of the most important changes in Uncanny Automator 4.13 is adding support for additional formatting in action token content when used in emails. We had feedback from the WPForms team that sending emails based on OpenAI responses was difficult in our previous version because proper paragraph formatting wasn’t retained. With the Uncanny Automator release, including GPT and other AI responses in emails now includes original formatting so that you can send responses to users as-is, without worrying about what it will look like to them.
There’s also a key terminology change that we’re making across Automator. We had too much confusion about what “premium” integrations meant, so we’re standardizing around “app” integrations instead. These integrations cover anything that’s not WordPress, like Google Sheets and Twitter. So instead of “credits”, you’ll start seeing “app credits”, and we now call non-Wordpress integrations “app integrations”. Hopefully this helps to make things more clear.
Finally, FluentCRM gains a “Contact ID” token for triggers that were missing it.
The full list of updates is available in the Uncanny Automator changelog.