Blogging · FramerBetaYour Framer CMS, written from Ocoya.
Publish articles straight into a Framer collection — title, formatted content, cover image and date filled in, and the site published for you. Or run it the other way: a new item in your CMS goes out to every network on its own.
One key from your project, pasted once.
Framer has no sign-in for apps. It has a Server API, opened with a key you make in the project’s own settings — so you decide which project, and the key reaches nothing else.
Make a key in Framer
Open the project in Framer, go to Site Settings → General and create an API key. Copy it, and copy the project’s address from your browser.
Site Settings → General → API KeysPaste it into Ocoya
Open Channels in Ocoya, choose Framer under Blogging, and paste the address and the key. Ocoya opens the project straight away to check the key works.
Channels → Connect channel → FramerChoose your collections
Every CMS collection in the project is listed. Each one you tick becomes a channel on your calendar and a trigger for your workflows.
ConnectedThe key opens one project. That is the whole of the access.
A Framer API key belongs to a single project, so connecting the blog never reaches your portfolio or a client’s site. Have three Framer sites? Connect each with its own key. Delete the key in Framer and Ocoya’s access ends with it.
- Made in Site Settings — nothing to install, no plugin
- One project per key, connected separately
- Delete the key in Framer to cut the access at once
API Keys
Keys let services reach this project through Framer’s Server API.
Connect FramerProject addresshttps://framer.com/projects/Harbour-Kitchen--x4TqFramer API key••••••••••••••••Connect FramerAny collection you manage can be a channel.
Once the key is in, every CMS collection in the project is listed. Tick the journal, the case studies or the changelog, and each becomes a channel: scheduled like any network and ready to start workflows. A collection a plugin keeps in sync is shown too, but greyed out — Framer only lets the plugin write to it.
- Every collection you manage yourself can be picked
- Plugin-synced collections are named, with the reason
- The same collection can receive articles and start workflows
Choose the collections to connectAn article in, a finished CMS item out.
Ocoya reads the collection’s fields and fills the ones an article has. The headline becomes the Title — and the slug — the article becomes formatted Content with real headings, lists and links, the first image becomes the Cover, and a Date field is stamped with the moment it was published. A Summary or Excerpt field gets the article’s excerpt.
- Fields are found by name and type — Title, Content, Cover, Date
- Markdown arrives as real formatted text
- A slug already taken gets -2, -3 instead of an error
A summer menu from the coast
## Straight from the boats
Grilled mackerel, sea herbs and the first tomatoes of the year.
Published to your site, or left for review.
Each Publish to Framer step chooses. Publish live adds the item and publishes the project to your domain, retrying if Framer is busy and taking the item back out if it still cannot — so a failed post never leaves a stray item behind. Keep as draft marks the item Draft, which Framer leaves out of every publish.
- Publish live: the item is added and the site published at once
- Keep as draft: it waits in the collection, unpublished
- Posts from the composer go live; workflows let you choose
Framer publishes a project as a whole, so any other unpublished changes in it go live with the article. Keep as draft if somebody is mid-redesign.
Publish to FramerIn FramerPublish liveKeep as draft Publish to FramerIn FramerPublish liveKeep as draftMarked Draft — left out of every publish until someone changes it.
Publish to FramerIn FramerPublish liveKeep as draft Publish to FramerIn FramerPublish liveKeep as draftMarked Draft — left out of every publish until someone changes it.
Add an item in Framer. Watch it share itself.
Write in your Framer CMS as you always do. Ocoya checks the collection every 15 minutes, and each new item that is not a draft goes out to Instagram, LinkedIn and Threads — with its title, its cover and a link to its page. Or run only when a field reaches a value, like Category is Menu.
- Runs for every new item that is not a draft, or only when a field matches
- Checked every 15 minutes — Framer sends no notifications
- Each item runs once, and items already there are left alone
- Add an AI step in between to phrase it for each network
New item in a Framer collectionJournal
Posted
Posted
PostedEvery field of the item, ready to use.
Each field of the collection is handed to the steps after the trigger under its own name, with the item's page on your site. A post can quote the title, a prompt can read the whole article, and the cover becomes the post's picture without anybody exporting it.
- Any field as {{trigger.field_name}}, named as in your collection
- The item’s page as {{trigger.url}}, read from your CMS page
- Picked from a list in the builder, with the newest item to test with
A summer menu from the coast
{{trigger.image}}In the builder, every field of the collection is offered by its own name with the newest item’s value beside it — pick it, test it, use it.
What teams do with it.
Framer is where the site is designed and published. These are the jobs that stop needing a copy and paste once Ocoya can write to its CMS and read from it.
Run your blog from an AI campaign
Start a blog campaign in Ocoya and each article lands in your Framer journal with its title, content, cover and date — published on the day you scheduled.
Announce every new item
Add a post in your Framer CMS, and a workflow shares it to Instagram, LinkedIn and Threads with its cover and link.
Publish release notes from your tools
Send each release to Ocoya’s webhook and publish it as an item in a Changelog collection — the site updates without anybody opening Framer.
Keep events current
Schedule event pages ahead in Ocoya and publish them into an Events collection on the day, alongside the posts that promote them.
Draft from a feed
Point a workflow at an RSS feed and let AI write a draft item for each new article, waiting in Framer for an editor.
Publish once, everywhere
Pick Framer alongside WordPress, Webflow and DEV.to and the same article goes to each, under its own rules and on the same calendar.
The details, before you plan around it.
These follow from how Framer’s CMS and Server API work, and from how Ocoya reads and writes them.
A blog campaign, straight into Framer.
Give an AI blog campaign a goal and a schedule, choose your Framer collection, and each article arrives as a finished item — title, formatted content, cover, date, excerpt — with the site published on its day, alongside the social posts that announce it.
How campaigns workYour project stays yours.
Ocoya opens the project only to do what you asked: list its collections, add the items it publishes, publish when you chose Publish live, and — for a workflow — read the collection it watches. It never edits an item your team created and never touches your pages or design. Delete the key in Framer and the access ends at once.
Read our privacy policyStart from an example
Announce every new Framer item on Facebook and Threads. Publish a blog campaign into your journal. Each one is a ready-made workflow you switch on in a minute.
See WorkflowsBefore you connect
Framer has no sign-in flow for apps. Its Server API is opened with a key made in a project’s Site Settings, and each key reaches that one project only. Make one under Site Settings → General, paste it into Ocoya with the project’s address, and delete it in Framer whenever you want the access to end.
Your calendar, writing to Framer.
Paste one key and choose your collections in a minute.