Connect Webflow
Connect your CMS collection directly or keep your automation webhook.
Connect a Webflow CMS collection directly, or keep your existing automation webhook. Your collection and page template control how the article appears on your website.
Before you start
Your site needs a blog CMS collection and a page template that displays it. Have access to the site's API settings and enough CMS capacity for new items. Publish the template in Webflow before expecting a live article URL.
Connect directly
- In Webflow, open Site settings → Apps & integrations → API access. Generate a site API token with Sites read and CMS read/write permissions. Copy it privately. Webflow's API setup guide explains token permissions.
- Open Plan → Schedule and publishing → Connect or manage a website → Webflow.
- Enter the token and choose Find my websites.
- Select your website and blog collection.
- Check the suggested fields for title, article content, short description and featured image. Choose any required defaults, such as an author or category.
- Choose Connect website, then select this connection as your publishing destination.
The article content must go into a Rich text field. A plain-text field cannot preserve headings, links, lists or tables. The slug is managed automatically.
Match your featured images
Select every image field that should use the article's cover. For example, a collection with separate card and hero images can use the same selected photo for both. Webflow imports the photo onto its own CDN and receives its alt text.
If an image field is required in your collection, an article with its cover removed cannot be sent until you restore a cover or change that requirement in Webflow.
Check the first article
Start with draft delivery. Inspect the item in the selected CMS collection and preview its page. Check required author/category defaults, the rich-text field and both card and hero images if your template uses them.
Live delivery publishes the individual CMS item. It does not publish unrelated site design changes. Your site and collection template must already be published for the public article URL to work.
Existing webhook connections
Open Already publishing through a webhook? in the Webflow card to manage your existing automation. Direct and webhook connections are separate destinations. Choose one for each article so your automation does not create a second copy.
Build the receiving workflow
Use your automation tool to create a public HTTPS webhook. Connect it to Webflow with permission to create CMS items in your destination collection.
Map the article title to the collection's name field, slug to slug, and content to its rich-text body field. Match any other required collection fields before enabling the workflow.
The article content is HTML. Do not map it into a plain-text field if you want tables, lists and links preserved.
Map featured_image_url to the collection's image field and featured_image_alt to its alt text. If your collection has separate card and hero images, map the same URL to both. A removed cover sends null image fields; do not reuse an old cover or create an invalid empty image object. Existing automation workflows may need this mapping added before their covers appear in Webflow.
Connect an automation webhook
Paste the webhook URL in Webflow integration settings and save it. Test connection sends a sample marked as a draft. Confirm that your automation respects the draft flag before testing.
A successful webhook test means the receiver accepted the payload. It does not prove that Webflow created or published the final item.
Respect draft and publish
The payload includes both isDraft and is_draft for compatibility. In Draft mode they are true. Your receiver must use those values when creating the Webflow item.
Do not configure the automation to publish every received item regardless of its draft flag.
Confirm the outcome
Preserve operation_id and revision. Deduplicate repeated operations so retries do not create duplicate CMS items. Return a meaningful destination result or use the publication receipt workflow supported by your integration.
Choose the Webflow destination in Plan → Schedule and publishing after connecting it. Inspect one draft in the actual Webflow site before enabling automatic live publishing.
If an item does not appear
For a direct connection, check the selected site and collection, token permissions, required field defaults and available CMS capacity. If the item exists but its page does not, confirm that the collection template is published and uses the expected URL.
For a webhook connection, inspect the receiving workflow's execution and field mapping. A successful webhook response is not proof of a CMS item. Site-wide publication and CMS-item publication are different actions in Webflow.
Disconnecting in outwrite.ai stops future delivery through that connection. It does not delete existing Webflow items. Revoke the site token in Webflow if you no longer need it.
