The Automizy WordPress plugin is a thin bridge. Contacts, automations and email analytics all live in Automizy's SaaS. Locally, the plugin stores an enable flag, the API token and the tracking domain in wp_options as a serialized array. Per-form list mappings sit in wp_postmeta when a Gravity, Fluent or Contact Form 7 integration is enabled, with the Automizy list ID and optional consent text stored alongside each form.

The default plugin UI exposes those settings one screen at a time. There is no list view of every bridge across the site, no filter for forms whose Automizy list was archived in the SaaS, and no diff between staging and production capture configs. Multisite operators have to log into each subsite separately to confirm the same plugin is wired the same way everywhere, which makes drift hard to catch until a campaign misfires.

SleekView reads each storage path directly and renders the integration as one table. The capture-script row sits at the top, form-bridge rows for each mapped form follow, consent text shows as a column, and a status pill flags rows whose Automizy-side target no longer responds. Edits route through the plugin's options API where supported so the same WordPress hooks fire as if the form was saved from its own settings screen.

Automizy is a SaaS-first product and its WordPress plugin is intentionally narrow: drop in a tracking script, bridge a few form plugins, hand the rest to the SaaS. That design is sensible until you have a site that has been live for two or three years and the WP-side state has drifted from the SaaS-side state without anyone noticing. Lists get archived in Automizy and mapped forms keep posting into the void.

Consent strings get rewritten by legal in the SaaS but the WP-side overrides still carry the old wording. Capture scripts get disabled on a page during a launch and never re-enabled. None of these failures surface in the default plugin UI because the UI is built around editing one thing at a time, not auditing the full inventory.

SleekView's contribution is structural: it turns each storage path into a column on a single table. Once the audit table exists, every drift problem becomes a filter and every fix becomes a bulk edit. For agencies running Automizy across multisite networks, the same table renders network-wide so an integration review is one screen rather than one screen per client.