Auto-promote Webflow blog posts to LinkedIn and X

Whenever I publish a new article to my Webflow blog, automatically promote it on LinkedIn and X. Build this as an agent workflow.

Trigger: a Webflow webhook on the Collection Item Published event, scoped to my blog collection (I will pick the specific site and collection during setup). The webhook payload includes the published item's ID and the collection ID.

Step 1. Call Webflow Get Collection Item with the item ID from the webhook to read the full fieldData. I care about: title, summary or excerpt, body content, hero image URL, slug, canonical URL, tags or categories, and publish date.

Step 2. The agent's main job is platform-aware rewriting. It should:

- Read the body and pull a real opening hook out of it (a surprising claim, a question, a sharp observation). Do not just template the title.

- Draft a LinkedIn post: longer, first-person, conversational, 3 to 6 short paragraphs. Open with the hook. End with a clear call to action and the canonical article URL. No more than one or two hashtags, and only if they fit naturally.

- Draft an X post: punchy, must fit within 280 characters including the link. One or two hashtags pulled from the post's tags. Include the canonical URL.

- Treat LinkedIn's voice and X's voice as genuinely different. Do not produce two posts that say the same thing in different lengths.

Step 3. Publish both. Call LinkedIn Create Post with the drafted LinkedIn copy (attach the hero image if one is present on the Webflow item). Call X (Twitter) Create Tweet with the drafted X copy.

Step 4. Log the result. Return a short summary: which article ran, the LinkedIn post URL or ID, the X tweet URL or ID, and any errors. If either platform fails, the other should still publish; do not block one on the other.

Guardrails: never publish a duplicate if the same Collection Item Published event fires twice for the same item ID. Skip drafts or items in non-published states. If the hero image URL is missing or invalid, fall back to a text-only LinkedIn post.

Additional information

What does this prompt do?

Watches your Webflow blog and kicks in the moment a new article is published.
Reads the full post (title, summary, body, hero image, tags) and picks an opening hook worth leading with.
Writes two distinct social posts: a longer, first-person LinkedIn version and a punchy X version that fits the character limit.
Publishes both to your LinkedIn profile and your X account, with a clean link back to the canonical article.

What do I need to use this?

A Webflow site with a blog or article CMS collection.
A LinkedIn account you can post from (personal profile or company page).
An X (Twitter) account you can post from.

How can I customize it?

Change the voice or tone (first-person vs brand voice, casual vs polished, with or without emojis).
Point it at a different Webflow collection: case studies, changelog entries, podcast episodes, or product launches.
Tighten the hashtag rules, force a specific UTM on the link, or skip hashtags entirely on LinkedIn.

Frequently asked questions

Does this work for any Webflow CMS collection, or only blog posts?

Any collection. You point it at the collection you care about (blog, case studies, changelog, podcast) and it runs whenever a new item is published there.

Will the LinkedIn and X posts say the same thing?

No. The agent drafts each one for its platform. LinkedIn gets a longer first-person take that opens with a hook from your article and ends with a call to action. X gets a shorter, punchier version with one or two hashtags pulled from your post tags.

Can I review the posts before they go live?

Yes. You can route the drafts to Slack, email, or a Notion page for approval and only publish after you give a thumbs up. Tell the workflow author you want a review step.

What if my post has no hero image?

The agent still publishes a text-only post. If a hero image is set in Webflow, it can be attached to the LinkedIn post.

Can I post to a LinkedIn company page instead of my personal profile?

Yes. If you have admin access to the page, you can target it directly. Same flow, just a different destination.