AutomatorWP plugin review and common issues

Go to AutomatorWP → Logs. Each automation run attempt is logged with status and any error messages. If the trigger is not listed in logs at all: the trigger may not be firing (check the trigger condition is met — user must be logged in if it is a user-specific trigger). If the trigger fires but actions fail: check the action configuration for missing required fields. Enable WordPress debug logging (WP_DEBUG) to capture any PHP errors during action execution that might not appear in the AutomatorWP log.

The WooCommerce add-on for AutomatorWP includes specific triggers for order status changes. In the automation trigger settings: select “WooCommerce: User completes a purchase” for order completion, or “WooCommerce: An order status changes” for any status transition with a specific status filter. Verify the trigger matches the actual WooCommerce order status — custom order statuses (e.g., added by WooCommerce Order Status Manager) may need their own trigger configuration or a different trigger condition.

Go to automatorwp.com/add-ons/ for the full add-on library. Some add-ons are free (like WordPress and basic WooCommerce) and available on WordPress.org. Premium add-ons (LearnDash, MemberPress, GravityForms, etc.) are purchased individually or in bundles from automatorwp.com. After purchasing, download the add-on zip file and install via WordPress → Plugins → Add New → Upload Plugin. Ensure the core AutomatorWP plugin is installed before any add-ons.

AutomatorWP is extensible via WordPress hooks. To register a custom trigger: (1) use the automatorwp_register_trigger hook to register your trigger with a unique ID and label; (2) hook into the WordPress action that fires for your custom event using add_action(); (3) inside the action callback, call do_action(“automatorwp_trigger_[your_trigger_id]”, $user_id, $trigger_args) to fire the AutomatorWP trigger; (4) AutomatorWP checks all active automations with that trigger and executes their actions. This approach allows integrating any custom plugin or theme event into AutomatorWP workflows.

AutomatorWP’s “Anywhere” trigger and bulk run features allow applying automations to existing users. Create a test automation with the desired actions. Then go to AutomatorWP → Logs → Bulk Run (if available in your version) to manually trigger the automation for all users matching a condition. For very specific bulk runs not covered by built-in bulk features, use AutomatorWP’s WP-CLI integration or create a custom WordPress script that manually fires the AutomatorWP trigger action for each user in a loop.

Uncanny Automator provides better out-of-the-box WooCommerce integration with more WooCommerce-specific triggers and a more polished interface. AutomatorWP requires purchasing the WooCommerce add-on separately but offers the core automation engine free. For a single site with WooCommerce, Uncanny Automator’s free tier may cover most needs, with Pro for complex flows. For agencies managing many sites needing WooCommerce automation, AutomatorWP’s add-on model may provide more predictable per-site cost control.

AutomatorWP’s core focus is WordPress plugin-to-plugin automation. External app integrations (Slack, Google Sheets, email marketing platforms) are available via specific add-ons or through webhook/Zapier triggers that connect AutomatorWP to external services. The ecosystem is less mature for external app connections compared to Uncanny Automator Pro or SureTriggers Pro, which provide more direct external app integrations.

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.