Uncanny Automator plugin review and common issues

Go to Uncanny Automator → Logs. The logs show each recipe run attempt with status (complete, failed, in progress). Find the failed run and check the error message. Common causes: (1) the trigger conditions are not fully met — “specific user” triggers only fire for the designated user, not all users; (2) the recipe is inactive (check the recipe status in the recipe list); (3) a required action field is empty or has an invalid value (e.g., a Mailchimp list ID that no longer exists); (4) a PHP error in another plugin is interrupting WordPress hook execution before Automator fires. Enable WP_DEBUG to capture PHP errors.

The WooCommerce Order Completed trigger fires when WooCommerce changes an order status to “Completed.” Verify: (1) the order is actually reaching “Completed” status — check the order status in WooCommerce → Orders → [order]; (2) the recipe uses the correct trigger type (WooCommerce → “A user completes a purchase” or “Order status changes to Complete”); (3) if manual status changes are not triggering the recipe, check if you are using the correct trigger variant (automatic completion vs manual completion have different triggers in some Automator versions); (4) verify the recipe is set to “Any user” if the trigger should fire for all customers, not just a specific user.

External app connections use OAuth tokens that can expire. Go to Automator → Apps and find the failing app connection. Click “Disconnect” then “Connect” to re-authorize via OAuth. For Google Sheets: ensure your Google account has the required permissions and Automator’s application is still authorized in your Google account security settings (myaccount.google.com → Security → Third-party access). Slack connections may also expire — re-authorize in your Slack workspace settings if the token is revoked.

Create a new recipe. Set the trigger: WooCommerce → “A user completes a purchase containing [specific product].” Add an action: LearnDash → “Enroll user in [specific course].” Save and activate. When a customer purchases the specified product and the order is marked complete, they are automatically enrolled in the LearnDash course. This automation eliminates manual course enrollment management for education businesses selling through WooCommerce.

Create a recipe. Set the trigger: WordPress → “A user registers on the site.” Add an action: Slack → “Send a message to a channel.” Configure the Slack channel (e.g., #new-registrations) and message body using Automator’s token system to include dynamic user information: {{{user_email}}}, {{{user_display_name}}}, {{{registration_date}}}. Save and activate. Connect your Slack workspace in Automator → Apps → Slack. New user registrations now send instant notifications to your Slack channel.

For WordPress-internal automation (automating between WordPress plugins), Uncanny Automator is significantly better: it runs on your server with no per-task cost, covers 170+ WordPress-specific plugins that Zapier doesn’t understand deeply, and is more cost-effective at high volume. For cross-platform automation between WordPress and non-WordPress services (Salesforce, HubSpot, Asana, etc.), Zapier has far more app integrations and more mature workflow logic. The typical best practice for WordPress sites is Uncanny Automator for WordPress-internal flows and Zapier/Make for flows that need external service integrations not covered by Automator.

The free version has no limit on recipe runs for WordPress plugin-to-plugin automation. A recipe can run thousands of times daily without cost or limit (beyond your server’s performance capacity). The only limitation is external app integrations, which require credits or Pro. For high-volume WordPress automation (e.g., processing thousands of WooCommerce orders daily, each triggering multiple actions), free Uncanny Automator handles this entirely within WordPress.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.