How Do I Auto-Share New Webflow Blog Posts to LinkedIn With Make?

Why am I still copying blog links to LinkedIn by hand?

You are copying links by hand because nothing connects your Webflow blog to LinkedIn yet. Every time you publish, you switch tabs, grab the URL, write a post, and paste it. Make can do that for you. It watches your Webflow CMS and posts to LinkedIn the moment a new article goes live.

I automated this because the manual step kept slipping. I would publish an article, get pulled into other work, and forget to share it for days. A post that no one sees is a post that does no work for you.

Make, the automation platform formerly known as Integromat, connects the two tools with no code. In this guide I will show you how I wire up a Webflow to LinkedIn flow, step by step, and the traps to watch for along the way.

What does this Make automation actually do?

This automation watches your Webflow blog collection and shares each new post to LinkedIn on its own. When you publish an article, Make notices, grabs the title and link, and creates a LinkedIn post. You publish once in Webflow, and the share happens without you touching LinkedIn at all.

In Make, a workflow like this is called a scenario. A scenario has a trigger that starts it and one or more actions that follow. Here the trigger is a new Webflow item, and the action is a LinkedIn post. That simple chain removes a chore you do every single week.

You can keep it basic or make it smart. A basic version posts the title and link. A richer version adds your excerpt, a hashtag, or a short line of context. I usually start simple, confirm it works, then add polish once the flow is stable.

What do I need before I start?

You need three things: a Make account, a Webflow site with a blog collection, and a LinkedIn account you can connect. For posting to a company page rather than your personal profile, you also need admin rights on that page, since LinkedIn controls who can post where.

A free Make account is enough to test this. Make measures usage in operations, which are the steps a scenario runs. A small blog that publishes a few posts a week uses very few operations, so cost is rarely an issue at this scale.

On the Webflow side, you just need your blog set up as a CMS collection, which most Webflow blogs already are. If you are weighing Make against other tools first, I compare them in my post on Make versus Zapier versus n8n.

How does Make know when I publish a new post?

Make knows through a Webflow trigger that watches your collection for new items. Make's Webflow app includes watch modules that fire when a collection item is created or published. You point that trigger at your blog collection, and it checks for new posts on a schedule you set.

This is the heart of the automation. Without a reliable trigger, nothing else matters. Make's Webflow modules can manage collections and items, so watching for a new published item is well within what the app supports. It polls your site at an interval, then passes any new item into the rest of the scenario.

The key detail is watching for published items, not just created ones. A draft is not ready to share. I always make sure the trigger or a later filter checks that the post is actually live before anything reaches LinkedIn.

How do I set up the Webflow trigger in Make?

Start a new scenario in Make, then add a Webflow module as the first step. Choose the watch option that fires on new collection items, and connect your Webflow account. Pick the site and your blog collection. Make will then pull recent items so you can see the fields it can read, like title, slug, and excerpt.

Connecting Webflow takes an authorization step, where you grant Make access to your site. Once connected, the module lists your collections. You select the blog, and Make maps every field in that collection. Those fields are what you will feed into the LinkedIn post next.

Set the trigger to run on a schedule that fits your pace. For a blog that posts daily, checking every fifteen minutes to an hour is plenty. There is no need to poll every minute, since that just burns operations for no real benefit. This is the same pattern I use for my Webflow CMS backup automation in Make.

How do I connect and format the LinkedIn post?

Add a LinkedIn module as the next step and pick the action that shares text, an article, or a URL. Connect your LinkedIn account, then map your Webflow fields into the post. I put the article title and a short line of context in the text, and the live URL as the link.

Make's LinkedIn app offers modules to share a simple text, article, or URL, including options to post on behalf of a company. You map the Webflow item's fields into these inputs. The post text can combine your title, your excerpt, and a fixed closing line, so every share reads cleanly.

Build the link carefully. Your Webflow blog URL follows a pattern, usually your domain plus slash blog slash the post slug. In Make, you join your domain with the item slug to form the full URL. Test one post to be sure the link resolves to the live article, not a staging or draft address.

How do I post to a company page instead of my profile?

To post to a company page, use the LinkedIn module option that shares on behalf of a company, and make sure your LinkedIn user has admin access to that page. This is the step people get stuck on. LinkedIn permissions decide whether Make can target your company page at all.

Make's community notes that some users connect their profile but cannot see how to aim posts at a company page. The fix is usually about permissions and picking the correct company action, not the automation itself. If the company option does not appear, check that your account actually administers the page.

If company posting gives you trouble, I suggest getting the flow working to your personal profile first. Prove the whole chain end to end, then switch the target to the company page. Splitting the problem makes it far easier to see where a setup breaks.

How do I avoid duplicate or premature posts?

Avoid duplicates by filtering for published items and letting Make track what it has already seen. Add a filter after the trigger so only live posts pass through. Make remembers which items it processed, so an item shares once. That combination stops draft posts and repeat shares from reaching LinkedIn.

A filter in Make is a simple rule between two steps. Here it checks that the item is published and, if you like, that it is not older than a certain date. Only items that pass the rule move on to the LinkedIn step. Everything else stops quietly.

Premature posting is the more embarrassing failure. You do not want a half-finished draft going public. That is why I filter on published status and test with a throwaway post first. Careful filtering is what makes the automation safe to leave running.

How do I test and turn it on?

Test by running the scenario once with a real recent post and watching each step. Make shows the data passing through, so you can confirm the title, link, and target are right. Once a test post lands correctly on LinkedIn, turn scheduling on so the scenario runs by itself.

I always run a manual test before going live. Make lets you run a scenario on demand and inspect the output of every module. If the LinkedIn post looks wrong, I fix the mapping and run again. It is much better to catch a bad link in a test than in front of your audience.

When the test passes, switch the scenario on and set its schedule. From then on, publishing in Webflow is all you do. The share takes care of itself. This kind of hands-off flow pairs well with an Airtable editorial calendar if you plan content ahead.

Should I automate social sharing this way?

Yes, if you publish regularly and keep forgetting to share. Automating the Webflow to LinkedIn hop saves time and makes sure every post gets seen. Just keep a light human touch, since a fully robotic feed can feel cold. I let Make post the link, then add a comment or reply myself.

Start with the simplest version that works, then improve it. Get one post sharing cleanly, add your excerpt and a hashtag, and only then think about company pages or extra networks. Small, tested steps beat one big complicated scenario that breaks in ways you cannot trace.

If you want help building automations like this around your Webflow site, from social sharing to full content pipelines, reach out. Setting up no-code flows that quietly handle the busywork is a big part of what I do, and I am happy to walk through your setup with you.