Uncanny Automator stores its no-code automations as uo-recipe custom posts. Triggers and actions are persisted as uo-trigger and uo-action child posts linked back to the recipe via post_parent. Run history lives in wp_uap_recipe_log and wp_uap_trigger_log, with completion counts updatable per recipe.

When ops shares a recipe URL into a thread, the default preview is the generic admin OG image. So 'Gravity Forms to HubSpot', 'WooCommerce to Mailchimp', and 'LearnDash to Slack' all preview with the same logo. Reviewers click through to find their bearings, which costs minutes per thread when you have dozens of recipes running.

SleekPixel reads the recipe post, counts its trigger and action children, and pulls the integration app names from the trigger meta. The card renders 'Gravity Forms then HubSpot' as a visual handle, with the live-or-draft state as a badge and the run count from wp_uap_recipe_log as an overlay.

Uncanny Automator scales from a single recipe to dozens or hundreds, especially in agencies running automations across many sites. Every recipe URL shared in a thread is a referent to a specific automation, and without a meaningful preview, every URL looks the same. Per-recipe cards turn a flat list of identical previews into a scannable inventory.

A reviewer pasted into a thread of ten recipe URLs can identify the cart-abandon recipe, the course-completion recipe, and the CRM-sync recipe from the previews alone, before clicking anything. That speed compounds across audits, handoffs, and incident reviews. The data was already in Automator's tables: the recipe post, the child trigger and action posts, the integration-app meta, the run log.

SleekPixel just composes them into an image and writes the og:image tag. No new tracking, no new automation, no extra workflow. The recipe URLs already get shared, and now they explain themselves.