How to publish AI content to WordPress and Webflow
Send finished content to WordPress, Webflow, Framer, Sanity or Ghost as a draft or live post, from an agent, a chat or a document.
Orchly agents can publish AI content straight to WordPress, Webflow, Framer, Ghost or Sanity, and send updates to Slack. You choose where the work goes in the agent’s Publishing row, and whether it lands as a draft or goes live. Everything an agent writes is also saved in Documents, so you can always review it in Orchly first.
Where can agents publish AI content?
| Destination | What the agent does | Setup |
|---|---|---|
| WordPress | Creates or updates a post | Connect WordPress |
| Webflow | Adds an item to a CMS collection | Connect Webflow, then map fields |
| Framer | Adds an item to a CMS collection | Connect Framer, then map fields |
| Ghost | Creates a post | Connect Ghost |
| Sanity | Creates a document | Connect Sanity |
| Slack | Posts a message to a channel | Connect Slack, add it under Apps |
The CMS has to be connected in Settings → Integrations first. See the integrations overview.
How to set an agent to publish
- Open the agent’s settings (the gear next to its name in the sidebar).
- In the Publishing row, switch on Publish to a CMS when complete.
- Click Choose destination… and pick your CMS. For Webflow and Framer, choose the collection and match Orchly’s fields (title, body and so on) to yours.
- Choose Save as draft or Publish live.
- Click Save (or Save Settings on a prebuilt agent).
The agent also needs the Publish on Site ability. Prebuilt agents keep their abilities fixed, but you can still set their Publishing row.
Save as draft puts the post in your CMS unpublished, so an editor can check it there. Publish live makes it public straight away. Start with drafts until you trust the agent’s output.
Review or Autopilot decides when it publishes
Publishing and Autonomy work together:
- On Review, the agent finishes the work and waits for your approval before it publishes. Content waiting for you shows in the Review column of the Content Agent board.
- On Autopilot, it publishes to your chosen destination as soon as it’s done.
So an agent on Review with Publish live still asks first. An agent on Autopilot with Save as draft publishes, but only as a draft.
Publishing from chat
In Ask Orchly, open + → Tools & data and switch on your CMS under Can post to. The agent can then publish a document it wrote in the conversation.
It always asks before it publishes, with an approval card marked Leaves Orchly, and it saves as a draft by default. See how approvals work in chat.
Publishing a document by hand
Open any document in Documents and click Publish. Choose Publish to platform and pick WordPress, Webflow, Ghost, Sanity CMS or Framer, then fill in the details in the panel that opens. If you’ve published it somewhere else already, use Mark as published instead.
After a document is published, the button reads Published and the menu offers Re-publish or update.
Sending results to Slack
Not everything is a blog post. A weekly visibility check or a list of pages losing clicks is better as a Slack message. Add Slack under the agent’s Apps row and set a Channel, then tell it in the instructions what to post, for example “Post a five-line summary of this week’s AI visibility changes to the channel.”
Sending a Slack message counts as leaving Orchly, so in chat it asks first. See connect Slack.
Internal summaries in Slack are fine on Autopilot. Anything that lands on your live site is safer as a draft or on Review until you’ve seen a few good runs.
Common questions
Can an agent send email? No. Agents publish to a CMS or Slack. Outreach emails are sent from the Activation Agent’s Backlinks tab. See backlink opportunities.
Why didn’t my agent publish? Check three things: the CMS is connected, the agent has Publish on Site (or your CMS is switched on in the chat), and its Autonomy isn’t holding the work for review.
Can agents change existing pages? The Site Health Agent can apply title, meta and schema fixes to live pages, after you approve them. See fix Site Health issues with an agent.