Sendy WP authenticates against a self-hosted Sendy instance (Sendy itself runs outside WordPress on a separate PHP host backed by Amazon SES). The plugin caches list IDs and the global API key in wp_options under sendy_settings, stores per-form list mappings in wp_postmeta (typically _sendy_list_id), and keeps a lightweight sync log of the last few hundred subscription events.

The default plugin screen shows a settings page and a per-form meta box, nothing more. Auditing which posts capture opt-ins to which Sendy list, or which form submissions never made it upstream after a Sendy outage, needs SQL against wp_postmeta and the plugin's sync log table. Cross-form questions like "which forms point at lists that no longer exist in Sendy" aren't surfaced anywhere in the admin.

SleekView reads the cached list IDs, the per-form _sendy_list_id postmeta, and the sync log together, then joins to wp_posts so every list mapping and every sync event renders as one filterable row. Inline retries route through the plugin's own sync handler so Sendy receives the event exactly as it would on a scheduled cron run.

Sendy is a self-hosted newsletter service that earns its place on the stack by trading the polish of hosted ESPs for cheap SES delivery at scale. The WordPress bridge is intentionally minimal: it forwards form submissions to Sendy and stores just enough state locally to retry on failure. That works fine until a site grows to dozens of forms and several lists, at which point the operational reality is that some events fail, some lists get renamed, and some mappings silently break.

The plugin's sync log table holds the truth about what happened, but there is no admin UI on top of it, so triage falls to whoever knows how to write SQL against the plugin's tables. SleekView lifts that table into a workspace with the form, list, and error string joined in line, retries that route through the plugin's own handler, and saved views for the questions that recur after every campaign. For teams committed to self-hosted email delivery, that workspace is the difference between an integration that scales operationally and one that quietly degrades.