Webflow integration
Approved work lands in Webflow, without copy-paste.
Create and publish Webflow CMS items through the Data API v2 with your field mapping preserved.
How it works
SearchHandled connects to Webflow through OAuth and the CMS Data API v2. During setup we map our content fields to your collection fields once (title, slug, rich text body, images, references, SEO fields), and every delivery after that follows the same mapping. Images are uploaded as Webflow assets before they are referenced, so nothing in your CMS points at an external host.
Webflow distinguishes staged items from live items, and since December 2024 the API supports publishing individual items rather than the whole site. We create items staged first, then make an explicit live-publish call per item when you approve. The API has no native scheduling, so when you schedule a post, we hold it and time the publish call for you at the moment you chose.
Best forDesign-led teams on Webflow who want CMS items created correctly against their existing collections without hand-copying content.
Setup, step by step
- Authorize SearchHandled through Webflow OAuth and select the site you want to connect.
- Pick the CMS collection that holds your blog or content items.
- Map your collection fields to SearchHandled content fields (body, summary, main image, SEO title and description, and any references).
- Run the connection check, which creates and removes a staged test item to verify write and publish access.
- Choose whether approved items publish live automatically or wait as staged items for your team.
What lands in Webflow
| Element | How it lands |
|---|---|
| Title and body | Converted to the native format, then verified by reading the entry back. |
| SEO metadata | Mapped to the platform's own fields, and flagged where it has none. |
| Images | Uploaded to your media storage with alt text. Never hotlinked. |
| Internal links | Rewritten to your live URLs and checked against redirects. |
| Publish state | Staged and live, per-item publish. |
Field mapping is confirmed against your own content model during setup. Connectors are on every plan; the number of connected sites is what varies.
Best practices
Keep a dedicated collection for pipeline content
Mapping is simplest and safest when SearchHandled writes to one clearly owned collection. Mixing hand-managed and pipeline-managed items in complex collections with many required references invites mapping surprises.
Watch your plan's item limits
Webflow caps CMS items per plan. If your collection is near its limit, deliveries will start failing at the cap, so check remaining capacity before ramping up volume.
Let images live as Webflow assets
Externally hosted images in rich text are unreliable in Webflow. We upload every image as a Webflow asset first; keep it that way rather than pasting external image URLs into delivered items later.
Stay inside Webflow's rich text feature set
Webflow rich text supports a specific set of elements, and content outside that set gets stripped. Design your templates around headings, paragraphs, lists, images, and quotes rather than custom embeds inside the rich text field.
Use it in the full SEO workflow
The connector is the last mile, not the strategy. Read the Webflow SEO automation workflow for the evidence gates, draft state, review rules, publish checks, and measurement loop that surround this integration.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Rate limits, including roughly one site publish per minute
Bursts of API calls or frequent publishes return 429 errors, which has broken Zapier and Make automations that assumed they could publish freely.
How we handle itWe queue writes with backoff that honors the Retry-After header, and we batch item creation and then publish once, rather than publishing per change.
developers.webflow.com, discourse.webflow.com, community.make.com
Created items invisible until published, silent publish failures
Items created through the API exist as staged items only, so they do not appear on the live site, and publish flows can fail without an obvious error.
How we handle itWe make an explicit live-publish call for each approved item and then read the live URL back to verify the content is actually serving before we mark the delivery complete.
discourse.webflow.com
Rich text mangles external images and strips embeds
External image URLs in rich text break or disappear, and HTML embeds are stripped from API-written rich text fields.
How we handle itWe upload all images as Webflow assets before referencing them and restrict output to the rich text subset Webflow reliably supports, so what we send is what renders.
discourse.webflow.com, wishlist.webflow.com
Questions teams ask
- Can posts be scheduled in Webflow?
Not natively through the API, which has no scheduling concept. We handle it on our side: the item is created staged, and we make the publish call at the scheduled time. From your perspective it behaves like scheduling.
- Will publishing an item republish my whole site?
No. We use per-item publishing, available in the Data API since late 2024, so approving a post pushes that item live without touching unrelated staged changes on your site.
- What happens if my collection hits its item limit?
Webflow rejects new items at your plan's cap. We surface that as a clear capacity error rather than a generic failure, and the fix is to upgrade the plan or archive old items.
Connect Webflow
One tested path from approval to publish.
Bring your content model to setup. We will map the destination and validate a draft before anything goes live.