SureTriggers plugin review and common issues

Check SureTriggers → Logs for the specific automation. The log shows trigger events and whether actions succeeded or failed, with error messages. Common issues: (1) the workflow is paused or inactive — check the workflow status; (2) a condition is blocking action execution — review any condition blocks in the workflow; (3) for external app actions, the connected app authorization may have expired — disconnect and reconnect the app in SureTriggers → Connections; (4) the 1,000 task/month limit (free plan) may be reached — check usage in SureTriggers dashboard.

Go to SureTriggers → Logs and find the specific workflow run. Check if the Google Sheets action shows as “Success” or with an error. If success but no data: (1) verify the Google Sheets spreadsheet ID and sheet tab name are correct in the action configuration; (2) check the column mapping — ensure field values are mapped to the correct spreadsheet columns; (3) verify the Google account connected to SureTriggers has write access to the spreadsheet; (4) test by manually running the workflow with a test trigger to see if the data appears.

Go to SureTriggers → Dashboard → Usage. The task counter counts each action execution, not each workflow run. A workflow with 3 actions uses 3 tasks per run. High usage often results from: (1) frequent triggers (every WooCommerce page view as a trigger in a high-traffic store); (2) workflows with many action steps; (3) test runs during setup that count toward the limit. Review each workflow’s trigger frequency and action count. Reduce trigger specificity if possible (e.g., only trigger on completed orders, not all order status changes).

Create a new workflow in SureTriggers. Set the trigger: WooCommerce → “New Order Placed” (or “Order Status Changed to Processing”). Add an action: Slack → “Send Message to Channel.” Configure the Slack channel (e.g., #orders) and message body with dynamic tokens from the order data: order number, customer name, order total, and products. Connect your Slack workspace in SureTriggers → Connections → Slack via OAuth. Activate the workflow. New orders now instantly notify your Slack channel.

In the SureTriggers workflow editor, between two action blocks, click the “+” button to add a step. Select “Delay” from the step options. Configure the delay duration (minutes, hours, or days) and whether it should delay only during business hours. The delay step pauses workflow execution and resumes at the scheduled time. Use delays for sequences like: “send welcome email immediately → wait 3 days → send onboarding tips email → wait 7 days → send check-in email.”

Both cover similar use cases with comparable pricing (~$149/year Pro). Key differences: Uncanny Automator has a longer track record, more WordPress-specific integrations, and is generally better for WordPress-internal automation where all actions stay on your server. SureTriggers has a cleaner interface, processes external integrations through its cloud (removing server load), and is more visually polished for non-developer users. Brainstorm Force backing gives SureTriggers strong development momentum. For Astra/CartFlows users, SureTriggers’ Brainstorm Force ecosystem integration is a natural fit.

Yes — SureTriggers supports LearnDash triggers (course completion, quiz completion, enrollment) and actions (enroll user in course, send notification). LifterLMS and other LMS plugins are also supported. Create automation workflows like “When a user completes LearnDash Course → send completion certificate email via Fluent SMTP → add user to Mailchimp audience → post celebration message to Slack.”

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.