SleekView for SureTriggers: workflow runs as customizable tables
SureTriggers (now OttoKit) keeps workflow definitions in its cloud, but every fire writes a row to wp_suretriggers_logs on your site. SleekView reads those rows directly so run-level triage stops requiring a dashboard login.
♾️ Lifetime License available
Local logs the official UI doesn't fully expose
OttoKit (the rebrand) hosts the workflow canvas in its cloud, but the plugin itself ships local tables. Version 1.1.0 added the per-site settings page and Detailed Logs feature. Version 1.1.4 added the Status / Clear-cache page. Both rely on wp_suretriggers_logs and a few related prefix tables that record every trigger fire, every integration outcome, and every outgoing API call count. That data is the local source of truth for what your automations actually did.
SleekView reads those tables through $wpdb and exposes the run log the way operators triage it. Time, trigger, integration, outcome, outgoing-call count, and status are sortable, filterable columns. Filter to integration equals Slack and outcome equals webhook 500 to find the rows the team is currently firefighting; sort by outgoing-call count to surface the runs eating into your OttoKit task quota disproportionately. The plugin's native UI shows the same data behind clicks; SleekView lets you query it.
The cross-blog story matters for agencies. OttoKit dashboards are workspace-bound, so a network running ten subsites with ten workspaces means ten dashboard logins to read the activity. SleekView aggregates the local logs across blogs and presents one cross-site activity view, which is the only practical way to answer "which workflow failed in the last hour, anywhere on this network?" The rebrand from SureTriggers didn't change the table names, so the same view keeps working.
Workflow
Triage OttoKit runs without leaving WordPress
Read the local logs
wp_suretriggers_logs and related prefix tables through $wpdb. The schema is detected at view-build time so version differences don't break the columns.
Pivot to run columns
Filter for the failure of the day
Hand off to the cloud when needed
Sample columns
A typical SureTriggers run log view
wp_suretriggers_logs (and related)
| Time | Trigger | Integration | Outcome | Outgoing calls | Status |
|---|---|---|---|---|---|
| Apr 24 09:14 | WC Order Created | Google Sheets | Sent 1 row | 1 | Success |
| Apr 24 09:12 | Form Submitted | FluentCRM | Contact created | 1 | Success |
| Apr 24 08:59 | WC Order Created | Slack | Webhook 500 | 3 | Retrying |
| Apr 23 22:10 | Course Completed | MailChimp | API 401 | 1 | Failed |
Comparison
Default OttoKit dashboard vs SleekView
Default OttoKit dashboard
- OttoKit dashboard requires a cloud login for every glance at logs
- Filtering local runs by integration + outcome takes several clicks
- Retry counts and outgoing-request totals aren't stacked in one column
- Multisite networks have to log in per workspace
- WP-CLI access to run history isn't exposed
SleekView
-
Read directly from
wp_suretriggers_logs - Filter by trigger, integration, and outcome simultaneously
- Inline-mark a run for re-run via the SureTriggers status page
- Surface outgoing-call count per run for cost/quota tracking
- Cross-site roll-up for agencies running OttoKit across clients
Features
What SleekView gives you for SureTriggers (OttoKit)
Run-level visibility
Every trigger fires through a row. Sort by duration, outgoing-call count, or outcome to find expensive or flaky runs before they show up as a billing surprise or a customer ticket.
Failure triage
Filter for failures by integration to see which downstream API is sick. Click into a run to view its payload and error message; the payload column links to the plugin's detail UI when you need it.
Multisite roll-up
Across networks, see every blog's last 50 runs in one cross-site activity view. The OttoKit dashboards stay per-workspace; SleekView gives ops the cross-cutting view they always lacked.
Audience
Who uses SleekView for SureTriggers
Automation owners
Watch live run health without bouncing to the OttoKit dashboard for every check. The filterable view is the difference between glancing at the system and logging in to read it.
Support
When a customer says "my email never arrived," find the matching run row in seconds by trigger and time. The outgoing-call count column tells you whether the integration even attempted the downstream send.
Quota management
Outgoing-call counts per run map directly to OttoKit task usage. Spot heavy workflows before billing surprises, and identify the recipes that grew their fan-out silently after an edit.
The bigger picture
Why local-first run logs change automation ops
Most automation platforms keep their run history in the cloud, which is fine until ten teams each need to know whether a particular workflow fired correctly in the last hour. OttoKit is unusual in that it writes the run log to local WordPress tables, and that locality changes the operational posture: you can run SQL against the data, you can join it to other WordPress tables (orders, users, posts), and you can audit it without a workspace login. The day-to-day friction is that the plugin's native UI was built around drill-downs into single events rather than around the dataset as a whole.
An operator chasing "which Slack-targeted runs failed today" wants to filter and sort, not paginate. The outgoing-call count is especially load-bearing because OttoKit task usage maps directly onto outgoing calls, and a workflow that quietly grew from one outgoing call to four per fire is the kind of cost surprise you only catch by looking at the dataset. SleekView treats the local log as the operational primitive it actually is.
Questions
Common questions about SleekView for SureTriggers (OttoKit)
No. Workflow definitions live in the OttoKit cloud, which is where you build, edit, and publish them. SleekView reads the local run log so ops can audit what actually fired and why. The two systems pair: define in OttoKit, observe in SleekView, with the local log as the source of truth for the observation half.
Recent versions install wp_suretriggers_logs and a few related prefix tables; the exact set depends on plugin version. SleekView reads them directly via $wpdb and detects the schema at view-build time. Version differences don't break the columns because the detection runs every time the view loads.
Version 1.1.4 added a Status / Clear-cache page with a re-run UI in the plugin. SleekView links to that UI for the selected row, so you stay in your normal table workflow until you actually need to re-fire. The link carries the run identifier so the plugin opens straight to the right entry.
Yes. Canvas-built and recipe-built workflows both write to the same local log tables. SleekView shows them all the same way, with the integration column reflecting whichever downstream service the workflow targeted. There is no separate code path for canvas vs recipe in the data layer.
The plugin slug stayed suretriggers; the UI rebranded to OttoKit. SleekView reads the same tables, so no migration is required. Existing views keep working through the rebrand. New subsites installing the OttoKit-branded build still write to the same prefix-tabled schema.
Yes. Each row records the integration. Combine that with outcome and duration columns to spot which integrations are slowest or flakiest in your specific setup. The filter is the fastest route to a vendor-specific incident: Slack failing, MailChimp 401-ing, Google Sheets timing out.
Yes, near enough that it's the right operational signal. OttoKit bills by task, and a task fans out into one or more outgoing calls. Sort by outgoing-call count and the high-fanout workflows show up first. That's the audit you want before you renew at the next plan tier than you actually need.
Retention is controlled by OttoKit's own configuration, not SleekView. The view reads whatever is currently in the local table, so a tighter retention setting produces a shorter table and a longer one produces more depth for trend analysis. Pair the audit with a backup of the table for compliance scenarios that need historical depth beyond the live retention.
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