How to connect Webflow to Orchly
Connect Webflow with a Site API token so Orchly agents can publish to your CMS collections and update page SEO fields.
To connect Webflow to Orchly, generate a Site API token in your Webflow site settings, then paste it into Settings → Integrations → Webflow and click Connect Webflow. Agents can then publish articles into your CMS collections and fix titles and descriptions on your pages.
How do I create a Webflow Site API token?
- In Webflow, open the site, then go to Site settings → Apps & integrations → API access.
- Click Generate API token and set these permissions:
- CMS: Read and write, to publish articles and fix SEO on CMS pages.
- Pages: Read and write, to fix titles and descriptions on static pages like Home and Services.
- Sites: Read-only, so Orchly can find the site.
- Everything else: No access.
- Copy the token. Webflow shows it only once.
If you lose the token, you’ll need to generate a new one in Webflow.
How do I connect the token to Orchly?
- Go to Settings → Integrations and click Configure on Webflow.
- Paste the token into the Site API token field.
- Click Connect Webflow.
Orchly checks the token with Webflow before saving it. If it’s wrong or missing permissions, you’ll see an error under the field. Once it’s saved, the badge shows Connected.
How do I map my CMS collection?
Webflow content lives in CMS collections, each with its own fields. Tell Orchly which fields to fill:
- Open the Webflow drawer again.
- Under Content mappings, click Map a collection.
- Pick the collection (for example your Blog) and choose what goes into each field: title, body, slug, excerpt and so on.
Without a mapping, articles publish as a single body, which usually isn’t what you want. See publishing agent output.
What can agents do in Webflow?
- Publish articles as new items in a mapped collection.
- Update existing items, for example refreshing an old guide with new stats.
- Fix SEO on CMS items and static pages: titles, meta descriptions and Open Graph fields. This is what the Site Health Agent uses.
Try asking Ask Orchly: “Which CMS items have no meta description?” or “Publish this article to the Blog collection”.
Changes to pages go live the next time you publish in Webflow. Orchly doesn’t trigger a site publish for you, so you stay in control of what goes live.
What can’t it do?
Schema markup can’t be added to a static page through a Site API token. Webflow only lets its own OAuth apps add custom code. When a fix needs schema, Orchly tells you to add it in Webflow under Page settings → Custom code.
Troubleshooting
| Problem | What to check |
|---|---|
| ”Could not connect Webflow” | The token is wrong, expired, or was created for a different site. Generate a new one with the permissions above. |
| Articles land as one big body | No collection is mapped. Click Map a collection in the drawer. |
| Page SEO fixes fail | The token is missing Pages: Read and write. Generate a new token with it. |
| A change isn’t live yet | Publish the site in Webflow. |
To remove Webflow, open its drawer and click Disconnect. For other CMS options, see the integrations overview.