AutomateWoo stores its marketing flows as aw_workflow custom posts, with rules, triggers, and actions persisted to its own tables: wp_automatewoo_logs for run history, wp_automatewoo_queue for scheduled runs, and meta on the workflow post for the trigger type. Every workflow has a unique admin URL that teams paste into Slack, Notion, and client docs whenever someone needs eyes on a specific automation.

The default preview for those URLs is the generic WordPress admin OG image, which means a winback flow, an abandoned-cart series, and a review-request automation all look identical when shared. Teammates have to click through just to know which workflow the conversation is about, even when only the name is needed.

SleekPixel reads the workflow post and the AutomateWoo trigger meta, then composes a card with the flow name, trigger type, number of steps, and current status. When the flow is paused, the badge changes. When the trigger or step count changes, the card refreshes on save.

AutomateWoo flows often live in a marketing team's daily flow of communication. A copywriter pastes the welcome series URL into a thread. An ops manager drops the cart-recovery URL into a debugging chat.

A client wants to see what is running. Without per-flow cards, every URL preview is the same admin chrome, so reviewers have to click each tab just to find their bearings. With SleekPixel, the workflow name, the trigger, the step count, and the active state are visible the moment the URL is pasted.

That visibility compounds when you have dozens of flows running. Pausing a flow becomes a visual change in every old link. Activating a new seasonal flow becomes immediately recognizable in shared docs.

None of this changes how the flows themselves work, only how the URLs read when they move through Slack, email, and internal documentation. The data was already in AutomateWoo's tables, just not in the share preview.