SleekView Charts for Uncanny Automator
Uncanny Automator writes every recipe run to wp_uap_recipe_log and every action to wp_uap_action_log. SleekView Charts groups those rows into success-rate donuts, busiest-recipe bars, and failure-per-hour trends.
♾️ Lifetime License available
Automation telemetry the plugin already records
Automator's logging is comprehensive: wp_uap_recipe_log for runs, wp_uap_trigger_log for triggers, wp_uap_action_log for actions, each with completion status, duration, and a foreign key back to the recipe. The default log UI nests those tables behind paginated screens, so finding 'how many recipes failed yesterday' means clicking through every recipe.
SleekView Charts reads the same wp_uap_* family and rolls it up. Total runs for the period, success-rate distribution, busiest recipes ranked by run count, and failures per hour are four chart cards that turn opaque log data into ops telemetry. Each chart joins to wp_posts for the recipe name and to wp_users for the triggering user, so labels read like 'WC order to Slack' instead of integer foreign keys.
Charts and Tables share the same data layer, so a filter applied on the recipe-log table (completed equals failed, last 24 hours) reshapes every chart on the dashboard. The plugin still owns recipe execution and notifications. SleekView Charts owns the operational visibility layer that long-running Automator installs need to stay healthy.
Workflow
From wp_uap_* tables to an automation dashboard
Map the log family
Join users and recipes
Build the success funnel
Trend failures over time
Sample dashboard
Charts you can build from Uncanny Automator data
Total recipe runs today
Count
Run outcomes
Count
group by completed
Busiest recipes by runs
Count
group by recipe_id
Failures per hour
Count
group by date
Comparison
Default Automator reporting vs SleekView Charts
Default Automator logs
- No aggregate dashboard across recipes
- Success-rate distribution is not visualised
- Cross-recipe run-count comparison requires manual counting
- Failure spikes are visible only by scrolling logs
- Average duration per recipe is not surfaced
SleekView Charts
- Total runs and success rate as Number cards
- Outcome donut for at-a-glance pipeline health
- Busiest-recipe bar with joined names
- Failure-per-hour line for incident detection
- Average duration per recipe as a sortable metric
Features
What SleekView Charts gives you for Uncanny Automator
Pipeline health donut
Count by completed status across every recipe. Finished, in-progress, and failed as proportions tell you within a glance whether the daily automation load is clean.
Busiest-recipe ranking
A horizontal bar of run count per recipe, joined to wp_posts for readable labels. Mission-critical automations and retirement candidates surface from the same chart.
Failure trend line
Failed-runs per hour as a line chart. A baseline plus a sudden spike is the earliest signal a Slack carrier or a Stripe webhook is broken.
Audience
Who builds Automator charts dashboards with SleekView
Automation troubleshooters
A live failures-per-hour line and a recent-failed-runs table on the same dashboard. Incident detection drops from days to minutes for silent automation breaks.
Operations leads
Busiest-recipe bars plus average-duration metrics show which automations carry the load and which run slow. Capacity planning becomes a screenshot, not an investigation.
Compliance and audit
Weekly run-volume and success-rate charts as evidence for SOC2 or ISO reviews. The dashboard answers 'is the automation layer healthy' without a custom report build.
The bigger picture
Automation at scale needs aggregate signals
Automator runs the quiet critical work: form to Mailchimp, order to Slack, course completion to CRM. When one of those recipes silently fails, the business consequence shows up days later in a missed lead or a missing contact. The default log UI is built for inspecting a single recipe at a time, which is the wrong surface for catching regressions across hundreds of runs per day.
Aggregate charts are the right surface. A donut of completed-status proportions tells you whether the day's automation load is clean before you read any individual row. A bar of run count per recipe ranks the busiest paths and surfaces the retirement candidates.
A line of failed-runs per hour is the earliest signal of an outage. None of this requires extra data: wp_uap_recipe_log already records completion, duration, and timestamps on every run. SleekView Charts adds the dashboard that turns those rows into ops telemetry, and the same data layer feeds the SleekView recipe-log table so drill-down from chart to row is one click.
The plugin keeps running recipes; the charts make running them at scale safe.
Questions
Common questions about SleekView Charts for Uncanny Automator
wp_uap_recipe_log for run-level metrics, wp_uap_action_log for action-level metrics, and the trigger logs for trigger-level metrics. Each can power its own dashboard, or you can combine them into a single ops view with cross-table joins.
Yes. SleekView Charts joins wp_uap_recipe_log.recipe_id to wp_posts.ID and uses post_title as the chart label. Bars and donuts read 'WC order to Slack' and 'Form to Mailchimp' instead of numeric foreign keys.
Yes. The wp_uap_* table family is the same on Free and Pro; Pro just adds extra metadata columns for premium triggers and actions. Charts read whichever tables your install has, so dashboards keep working through upgrades and downgrades.
Yes. The recipe log records start and end timestamps. A bar of average duration per recipe surfaces slow automations; a line of average duration over time catches regressions. Useful for spotting a recipe that started taking three times as long after a plugin update.
No. Charts read with cache-duration controls and hit indexed columns where Automator has indexes (run_number, completed, date). The recipe-execution path is untouched. A dashboard refresh is read-only against the log tables.
Yes. Charts and Tables share the same data layer. Clicking a chart segment scopes the matching SleekView recipe-log table to that cohort, so 'failed runs in the last hour' goes from a chart spike to a sortable list in one click.
Yes. The recipe log carries the triggering user ID. Charts can group by user (joined to wp_users for the email) to see whose actions trigger the most automations, or to scope a dashboard to one team's activity.
Yes. Each chart card exports as a PNG image and as CSV data. Weekly success-rate trends and run-volume histories are exactly the kind of evidence SOC2 or ISO auditors ask for, and the export respects the current filter.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout