The category-exclusion check in step five is the one most teams forget, and it’s usually how an internal-only post ends up live on the company LinkedIn page. Run this prompt before building the recipe so that check gets baked in from the start rather than added after an incident.
Automation
Auto-post new blog content to social media on publish
A scenario prompt that turns a described publish-to-social workflow into a recipe covering scheduled posts, image fallbacks, and per-platform caption limits.
Works with Claude / GPT530 uses★ 4
The prompt
automation-content-publish-to-social-media-post
A content team describes their process like this: "When a blog post is published on WordPress, I want it automatically posted to our LinkedIn company page and X account with the title, a short excerpt, the featured image, and a link back to the post." AVAILABLE TOOLS: [WordPress publish event (trigger), Uncanny Automator, LinkedIn, X (Twitter)] Turn this into an implementation-ready automation recipe, thinking through what the plain description leaves ambiguous: 1. Trigger: the exact event to fire on, since WordPress fires a "publish" transition both for a brand-new post and for an old post being republished or updated. Decide whether updates should re-post or be excluded entirely. 2. Conditions: what happens when a post is scheduled for the future and published automatically by WordPress's cron at 3am. Should the social post fire immediately, or is there a business reason to delay it to a normal posting-hours window. 3. Actions in order: pull the featured image (with a fallback to a default brand image if none is set, since a caption with a broken image link looks worse than no image), truncate the excerpt to fit X's character limit without cutting a word mid-way, then post to LinkedIn first and X second so a partial failure doesn't leave X live without the LinkedIn version. 4. Failure handling: if the X post fails due to a rate limit but LinkedIn succeeds, should the recipe retry X alone, and how many times before alerting the content team via Slack or email. 5. One edge case specific to this exact workflow: a post published in a category tagged "internal" or "draft-notes" that should never go to social. Confirm the recipe checks category before posting, not just publish status. Replace the workflow description and available tools with your own.