Munshi and Framer
Munshi Social, the AI content marketing engine for small teams, writes SEO articles intoFramer from the same weekly plan as every other channel. SEO articles land as draft items in your Framer CMS collection, for you to publish.
14-day free trial · No card required · 7-day money-back
A finished article as a draft item in your Framer CMS blog collection, in Framer's rich text. You review it in Framer and un-draft it to publish.
How the connection works
You create a Server API key in Framer (Site settings, Server API) and paste it into Munshi with your project URL. Munshi picks the blog collection for you. You can revoke the key in Framer at any time.
What comes back
Search Console and Google Analytics numbers for every article, on the Results page next to your social results.
How articles land
- Articles always land as drafts and stay drafts until you un-draft them in Framer, even when the site is published
- Ghost, Webflow, and Framer receive articles as drafts you publish from your own dashboard. WordPress takes drafts too, except scheduled articles, which go live at their slot. Sanity goes live, now or on schedule.
What to know
- Framer's Server API is in beta, so Framer may change it, and Munshi tracks those changes
- The cover image is not written into the collection, so add it in Framer when you publish
- One Framer project per workspace
Munshi writes SEO articles and saves them in your Framer CMS blog collection as draft items. Each item gets the title, slug and body, in Framer's own rich text. The cover image is not sent, so you add it in Framer.
The item stays a draft until you un-draft it in Framer, even after the site is published. That is Framer's own model, not a rule Munshi added, and it means nothing you have not read can reach your readers.
Connecting takes two things: your project's URL and a Server API key, a password Munshi uses to publish. You create the key in the project's own settings. Munshi then reads the project's collections and picks the one that looks like your blog, so there is usually no ID to hunt for.
What you can post to Framer
| Format | What goes out |
|---|---|
| The body | HTML into the collection's formatted text field. Headings, lists and links arrive as Framer's own rich text, not raw markdown. |
| Title and slug | The article's title, and the Slug from its SEO fields, which becomes the item's slug in the collection. |
| The collection | Munshi picks it: the first collection whose name contains blog, post, article or news. Failing that, it takes the first with a formatted text field, then the first collection. Paste a Collection ID only to override that. |
| The cover | Not sent. The bridge Munshi publishes through writes formatted text, not images, so add the image to the item in Framer before you publish it. |
| Published or scheduled | A draft item, either way. It carries Framer's own draft flag, so it cannot go live with the site. Munshi says it was saved as a draft in your Framer CMS and names the collection it went to. |
How to connect Framer
-
Open Integrations
Click Settings at the bottom of the sidebar, then Integrations. Framer is one of the blogs under Publish your blog. Only the workspace owner can save a blog connection.
-
Open the Framer card
Click Framer. The card asks for a Project URL and a Server API key, with Collection ID below them marked optional. Your project URL starts with https://framer.com/projects/ and then your project's own part.
-
Create a Server API key
In Framer, open the project's Site settings, then Server API, and create an API key. Paste it into Server API key, where it shows as dots, beside the project URL. Save stores it encrypted on Munshi's server. You can revoke the key in Framer at any time.
-
Leave Collection ID empty
Munshi finds the blog collection itself. It takes the first collection whose name contains blog, post, article or news. Failing that, it takes the first with a formatted text field, then the first collection in the project. Paste an ID here only when you want a different one.
-
Save and see the collections
Click Save. Munshi connects to the project with the key. When Framer accepts it, the card reads Connected and names every collection it found. It also reminds you that a Collection ID overrides the one it picked.
Drafts stay drafts until you un-draft them
Items Munshi writes carry Framer's own draft flag, so publishing the site does not publish them. The article waits in the collection until you un-draft it in Framer. A site rebuild for some other reason can never push out a piece you had not finished reading.
Scheduling sets when Munshi sends the item, not when it appears. At the slot the article is sent again, still a draft. It reaches readers only once you un-draft it in Framer.
Framer's Server API is still in beta
Framer's Server API is in open beta and free while the beta lasts, and Framer can still change it. Munshi publishes through a small bridge that runs Framer's official SDK, its developer toolkit, pinned to a known version. So a change on Framer's side is something Munshi follows, not something that quietly breaks your publishing.
The beta has two effects. The check can time out when Framer is slow, and clicking Check again a minute later is usually all it needs. And you remove a published item in Framer, because Munshi does not take items back out of the collection.
The cover is not sent to Framer
Munshi builds a cover for every article from your brand kit at the Featured Image step. It goes out with the article on WordPress, Ghost, Sanity and Webflow. Framer is not one of those. The bridge writes formatted text, not images. So the item arrives without a picture.
Add the picture to the item in Framer before you un-draft it. The cover Munshi built stays on the article's Featured Image step, tagged Generated from your brand kit, at 1200 by 630 pixels.
One blog per workspace, and you pick it
A workspace publishes its articles to one blog. With only Framer connected, articles go there. Publishing to at the top of Integrations names it by the address in your project URL.
Connect a second blog and publishing stops with More than one blog is connected until you choose one under Publish your blog.
The badge beside the destination reads Saved until a check passes again, which is normal after you close Settings. Click Manage, then Check, and it turns Connected.
Munshi and Framer, answered
Does Munshi work with Framer?
Yes. A finished article as a draft item in your Framer CMS blog collection, in Framer's rich text. You review it in Framer and un-draft it to publish.
Does Munshi publish to Framer, or only draft?
Only draft. Articles arrive as draft items in your CMS collection and stay drafts until you un-draft them in Framer, even after the site is published. That is the same whether you publish now or schedule the article.
Where does the Server API key come from?
From the project's own settings in Framer: Site settings, then Server API, then create an API key. Paste it into Munshi with the project URL. You can revoke it in Framer at any time.
Do I have to choose the collection?
Usually not. Munshi takes the first collection whose name contains blog, post, article or news. Failing that, it takes the first with a formatted text field, then the first collection. Paste a Collection ID to override that.
Is Framer support stable?
Framer's Server API is in open beta, so Framer may still change it. Munshi publishes through Framer's official SDK, pinned to a known version, and follows those changes.
Will the cover image appear in Framer?
No, not on its own. The item is written with formatted text and no images, so add the image in Framer before you un-draft it. The cover Munshi built is on the article's Featured Image step.
If I edit the article and publish again, do I get two items?
No. Munshi keeps the item's id and updates the same draft item rather than creating a second one.
Can Munshi remove an article from Framer?
No. You remove an item in Framer. Munshi writes and updates items, but it does not take them back out of the collection.
Can I connect two Framer projects?
Not in one workspace. A workspace holds one blog connection per platform and publishes to one destination. The Studio plan covers three brands, each with its own connected blog and calendar.
When Framer says no
These are the messages people see most often, and what each one means.
“Framer refused the connection”
Framer did not accept that project URL and key together. Check that the URL is the project's own, and that the key was created in that project's site settings. Then click Save again.
“Connected, but this Framer project has no CMS collections yet.”
The key works, but the project has no collection to put articles in. Add a CMS collection for your blog in Framer, then click Check.
“Framer did not answer in time. Try again in a minute.”
Framer took too long to answer the check. Click Check again shortly.
“Add your Framer project URL and API key first.”
Check ran before both were saved. Fill in Project URL and Server API key, then click Save.
The article went to the wrong collection
Munshi picked the first collection whose name suggests a blog. Copy the right collection's ID from Framer, paste it into Collection ID, and click Save. Articles go there from then on.
I published my Framer site and the article is still not live
Items Munshi writes carry Framer's draft flag, so publishing the site leaves them alone. Open the item in Framer and un-draft it.
Framer, step by step
Each guide walks through one task in the real app, with a screenshot at every step.
- How to connect Framer with a Server API key 3 min · 7 steps
- Draft or live: how an article lands in each CMS 3 min read
- How to choose where articles publish when two blogs are connected 2 min · 6 steps
- “More than one blog is connected” and other CMS refusals 2 min read
- How to set the SEO fields and publish, now or on a schedule 3 min · 10 steps
- How to choose a cover for an article 2 min · 8 steps
- How to copy or download an article for a platform Munshi does not connect to 2 min · 7 steps
Other blog platforms: WordPress · Ghost · Webflow · Sanity · all integrations