Home Developers & Integrations

Developers & Integrations

API, SDKs, MCP, and automation.
By BulkPublish Support
• 8 articles

Sharing Webflow CMS items to your channels

Link a Webflow site and BulkPublish can turn each new item in a CMS collection (a blog post, a case study, a product, an event) into a social post with its title, a short summary, its image and a link back to the page. Linking a Webflow site Workspace owners and admins can link sites from Share from Webflow in the Compose menu. 1. Click Link Webflow sites. 2. Webflow asks you to choose the sites BulkPublish may use and to approve access. Choose your sites and click Authorize app. 3. You return to BulkPublish, and each site you chose is listed. If you choose Cancel on Webflow's screen instead, nothing is linked and you can try again whenever you like. You can also start from the BulkPublish listing in the Webflow Marketplace. You are asked to sign in to BulkPublish (or create a free account) first, then Webflow's approval screen opens. Setting up a collection Under a linked site, click Add collection and choose: - Collection - the CMS collection whose items are shared. - When to share - When an item is published, or When an item is created, even as a draft. - Fields - which fields give the post its title, summary, image and link. The link is built from the site's address, an optional folder (for example blog) and the item's slug. - Caption - a template using {{title}}, {{summary}} and {{url}}. - Channels - where the posts go. The preview on the right shows how an item will look on each channel. Long text is shortened to fit each channel, and the link is kept whole. What happens when you publish Publish in Webflow as usual. Within a minute or two the post appears in BulkPublish, on your Calendar, where it follows your workspace's approval settings. - Editing an item that was already shared does not share it again. - Archived items are not shared. - Publishing the same item a second time does not create a second post. If you publish many items at once, they are shared over a few minutes. When an item is not shared When an item could not be shared, its collection shows the reason, for example an empty title field, a channel that needs reconnecting, or a plan limit. Fix the cause, then choose Try again from the collection's ⋯ menu. If we could not confirm whether an item's post was created, the collection says so. Check your Calendar first, and choose Share again only if the post is not there. If a site shows Needs linking again, Webflow is no longer accepting the connection (for example, the app was removed in Webflow). Nothing is shared until you click Link again. Items published in the meantime are not shared automatically; publish them again after relinking. Changing the site address Links use your site's custom domain, or its webflow.io address if it has none. To use a different address, click Edit site address. Unlinking a site Click Unlink on the site and confirm. BulkPublish's access to that site is removed straight away, along with its collection settings. Posts that were already created stay in BulkPublish. You can also remove BulkPublish from your Webflow workspace under Apps & Integrations. The site then shows Needs linking again in BulkPublish.

Last updated on Nov 01, 2026

Sharing Squarespace products and blog posts to your channels

Connect a Squarespace site and BulkPublish can turn each new product in your store, and each new post on your blog, into a social post with its title, a short summary, its image and a link back to the page. Connecting a site Workspace owners and admins can connect a site from Share from Squarespace in the Compose menu. 1. Click Connect a Squarespace site. 2. Squarespace asks you to approve access. BulkPublish asks only to read your products. It cannot see your customers, orders or payments, and it does not change anything on your site. 3. You return to BulkPublish, and the site is listed. If you decline on Squarespace's screen, nothing is connected and you can try again whenever you like. Turning on Products or Blog posts Each site has two parts you can turn on separately: - Products - shared when a product is added to your store. - Blog posts - shared when a post appears in your blog's feed. This needs your blog's address (for example https://yoursite.com/blog); add it with Edit. For each, choose the channels and write a caption template, then click Turn on. A preview shows how an item will look on each channel. Long text is shortened to fit, and the link is kept whole. What gets shared New items are picked up within about 10 minutes, and each post appears on your Calendar, where it follows your workspace's approval settings. - Anything already on your site when you turn sharing on is left alone. To share one of those, choose Share an older product or Share an older post from the ⋯ menu. - Hidden products are not shared. - Each item is shared once. A blog that is password-protected or for members only cannot be read, so its posts cannot be shared. The page says so if this happens. When an item is not shared When an item could not be shared, Products or Blog posts shows how many and why, for example a channel that needs reconnecting or a plan limit. Fix the cause, then choose Try again from the ⋯ menu. If we could not confirm whether an item's post was created, it says Check Calendar. Look on your Calendar first, and choose Share again only if the post is not there. If a site shows Needs connecting again, Squarespace is no longer accepting the connection. Nothing is shared until you click Connect again. Disconnecting a site Click Disconnect on the site and confirm. Its settings are removed from BulkPublish, and posts already created stay where they are. To stop for good, also remove BulkPublish from the connected apps in your Squarespace settings. If you remove it there first, BulkPublish removes the site on its side too.

Last updated on Nov 01, 2026

Sharing what you ship in Linear

Connect your Linear workspace and BulkPublish can prepare a social post each time your team finishes something worth announcing: a completed project, or a completed issue that carries a label you choose. Connecting Linear Workspace owners and admins can connect Linear from Share from Linear in the Compose menu. Choose Connect Linear, and Linear asks you to approve access for BulkPublish. The access is read-only: BulkPublish does not create, edit or comment on anything in Linear. When you approve, you come back to BulkPublish and your Linear workspace is listed on the page. A Linear workspace can be connected to one BulkPublish workspace at a time. Choosing what is shared On the Share from Linear page you can choose: - Completed projects. When a project is marked completed, a post is prepared from its name and description. - Completed issues with a label. When an issue carrying your chosen label (share unless you change it) is completed, a post is prepared from its title and description. Issues without the label are left alone, so you decide which work is worth announcing by labelling it in Linear. - Channels. The social accounts the post is prepared for. The post usually appears within two minutes of the work being completed in Linear. Work completed while sharing is switched off is not shared later. Drafts or publishing right away New posts start as drafts on your Calendar. Titles in Linear are usually written for your team, so a draft gives someone the chance to rewrite it for your followers, add an image and pick a time. If you would rather publish as soon as the work is completed, choose Publish right away. Posts still follow your workspace's roles and approval settings, so a post that needs approval waits for it. Caption templates Each kind of post has a template. You can use {{title}}, {{summary}} (the opening of the description), {{identifier}} (such as ENG-123, issues only), {{project}} (the issue's project) and {{workspace}}. Text that is too long for a network is shortened to fit, starting with the summary. Links to Linear are not added to the caption, because only members of your Linear workspace can open them. If you publish release notes or a changelog, add its address to the template. Each item is shared once A project or issue is shared the first time it is completed. If it is reopened and completed again, no second post is prepared. The Recently shared list on the page shows what was shared, with a link to each post. When something is not shared The page shows the reason next to the item, for example: - None of the chosen channels are connected any more. Choose channels again on the page. - Your plan's post limit was reached. The item can be shared the next time it qualifies, once there is room. - Linear no longer accepts this connection. Someone removed the app in Linear or the access expired. Choose Connect Linear again. - Paused. The person who connected Linear has left the workspace or can no longer create posts. An admin can connect Linear again from their own account. Disconnecting Choose Disconnect on the Share from Linear page. Nothing more is shared, BulkPublish's access to Linear is removed, and posts that were already created stay on your Calendar. You can also remove BulkPublish from your Linear workspace's settings.

Last updated on Nov 04, 2026

Sharing your Ghost posts to social media

Every Ghost site has a public feed of its latest posts. Add that feed to BulkPublish and each new post you publish in Ghost becomes a social post, with its title, excerpt, feature image and a link back to the article. There is nothing to install on your Ghost site. Finding your Ghost feed Your feed is your site address followed by /rss/, for example https://yourblog.com/rss/. Open it in a browser to check: you should see a page of your recent posts. Ghost also has a feed for each tag and each author: - https://yourblog.com/tag/news/rss/ shares only posts tagged news - https://yourblog.com/author/jane/rss/ shares only Jane's posts Use one of these when you want to share some posts and not others. A common setup is a tag such as social that you add in Ghost to the posts you want shared. Adding it to BulkPublish 1. Open Publish from RSS from the Compose menu and choose Add feed. 2. Paste your Ghost feed address. 3. Choose the channels the posts go to. 4. Under Post as, choose Save as draft to review each post before it goes out, or Publish automatically to share as soon as a new post appears. 5. Save the feed. The preview beside the form shows your latest Ghost post as it would appear on each channel, so you can check the wording and image before you save. Your existing posts are left alone When you add the feed, the posts already in it are noted and not shared. Only posts you publish after that become social posts, so adding a blog with years of archives does not flood your channels. How quickly new posts are shared Your feed is checked every hour on the Free and Lifetime plans, every 30 minutes on Pro, and every 15 minutes on Business. A post published in Ghost is shared at the next check. Choosing what the post says By default a post is the article's title followed by the link. In Caption you can write your own template using the article's Title, Link, Summary, Full text, Author and Categories (your Ghost tags), and give a channel its own wording, so the same article can read differently on LinkedIn than on X. Your post's feature image is attached automatically. That matters for Instagram and Pinterest, which do not accept a post without a picture. YouTube needs a video, so Ghost articles are skipped on YouTube channels and the feed tells you why. Plans Free workspaces can add one feed, and its posts are saved as drafts for you to review. Paid plans can publish automatically and add more feeds: 3 on Lifetime, 10 on Pro and 50 on Business. Posts created from your feed count toward your normal posting limits. If something is not shared If your Ghost site cannot be reached, the feed shows the last error so you can see what went wrong, and it is checked again later. You can pause a feed at any time without deleting it. If a post is missing, open your feed address in a browser and check it is listed there: Ghost pages are not part of the feed, and a tag feed only lists posts with that tag.

Last updated on Nov 04, 2026

Auto-connect your team's AI assistant

If your team uses BulkPublish from Claude, auto-connect lets everyone in your organization use it straight away. Nobody has to sign in to BulkPublish from Claude or paste an API key: your organization vouches for each person, and BulkPublish connects them to your workspace. Auto-connect works with Claude Team and Enterprise organizations. It can trust either your Claude organization or your company's identity provider. Before you start - You need to be the owner of the BulkPublish workspace. Admins and other roles can see the setting but cannot change it. - On the Claude side, you need to be an Owner or Primary Owner of your Claude organization. - Everyone who should be connected needs to be a member of your BulkPublish workspace, with a verified email address that matches the one they use in Claude. Invite anyone who is missing from Team first. Setting it up with your Claude organization 1. In Claude, open Organization settings, then Connectors, find BulkPublish and choose Set up auto-connect. For Identity source, choose Claude-issued. Claude shows an Issuer URL. Copy it. 2. In BulkPublish, open API in the sidebar and find MCP Auto-connect, below API Keys. 3. Paste the Issuer URL into Trusted issuer URL and choose Save. 4. Switch on Connect members automatically. 5. Back in Claude, choose Run test under Connection status to check that it works. From then on, when a member of your Claude organization uses BulkPublish in Claude, they are connected to your BulkPublish workspace as themselves, with their own role. Setting it up with your identity provider If your organization signs in to Claude through its identity provider, choose IdP-managed in Claude's auto-connect setup instead, and follow the steps it shows to register BulkPublish with your identity provider. Then paste your identity provider's issuer URL into Trusted issuer URL in BulkPublish and switch on Connect members automatically. Several workspaces, one organization If more than one of your BulkPublish workspaces trusts the same issuer, BulkPublish needs to know which workspace a person belongs in. Copy the Workspace ID shown under MCP Auto-connect and enter it as the Tenant ID in Claude's auto-connect setup for that workspace. Without it, sign-ins for that issuer are refused rather than sent to the wrong workspace. Who gets connected - Only people who are already members of the workspace. Auto-connect never creates an account or adds anyone to your team. - A person is matched by their verified email address. If their address in BulkPublish is not verified, or differs from the one their organization signs them in with, they are not connected. They can still connect the usual way. - Each person acts with their own role. A Viewer stays a Viewer. - An auto-connected assistant can work with posts, media, analytics and your inbox. It cannot manage your team, billing, workspace settings or API keys. Turning it off Switch off Connect members automatically. Everyone who was connected this way is disconnected straight away, not when their session would have ended. Changing the Trusted issuer URL does the same for everyone who was connected through the old one. Removing someone from your BulkPublish workspace also ends their access at once. Removing them from your Claude organization stops new connections, and any session they already had ends within the hour. Each person's connection is also listed under Connected apps as BulkPublish MCP (auto-connect). While auto-connect is on for the workspace, disconnecting it there ends the current session, and the next time that person uses BulkPublish in Claude they are connected again. When it does not connect - Run test fails in Claude: check that the Issuer URL in BulkPublish is exactly the one Claude shows, including any slash at the end, and that Connect members automatically is on. - One person is not connected: check that they are a member of the workspace and that their email address in BulkPublish is verified and the same as their Claude account's. - Nobody in a second workspace is connected: enter that workspace's ID as the Tenant ID, as described above. Still stuck? Contact support from the chat button in the app and tell us your workspace ID.

Last updated on Nov 06, 2026