Overview
The Webflow connector integrates with Webflow’s CMS API to publish articles directly to your Webflow collections. It supports:- Publishing to any CMS collection
- Flexible field mapping for custom collection structures
- HTML content formatting optimized for Webflow
- Category and tag synchronization
- Scheduled publishing
Prerequisites
Before connecting, ensure you have:- Webflow site with CMS enabled
- CMS Collection for blog posts/articles
- API token with CMS write permissions
- Site ID from your Webflow dashboard
Setup Guide
Step 1: Get Your Site ID
- Go to your Webflow dashboard
- Open your site’s settings
- Find the Site ID in the URL or settings panel
Step 2: Create an API Token
- Go to Webflow Dashboard → Account Settings → Integrations
- Or visit webflow.com/dashboard/account/integrations
- Click Generate API Token
- Select the sites you want to grant access to
- Enable CMS permissions (read and write)
- Copy the generated token
Step 3: Get Your Collection ID
- In Webflow Designer, go to CMS Collections
- Select your blog/articles collection
- The Collection ID is in the URL:
collections/{collection-id}
Step 4: Configure Field Mapping
Map Skayle fields to your Webflow collection fields:Step 5: Configure in Skayle
- Go to Settings → Connectors in Skayle
- Select Webflow as your connector type
- Enter your configuration:
| Field | Description | Example |
|---|---|---|
| Site ID | Your Webflow site ID | abc123xyz |
| Token | API token | wf_... |
| Collection ID | Blog collection ID | def456 |
| Title Field | Field slug for title | name |
| Slug Field | Field slug for slug | slug |
| Content Field | Field slug for body | post-body |
| Excerpt Field | Field slug for excerpt | post-summary |
- Click Test Connection to verify
Webflow Collection Setup
Here’s a recommended collection structure for blog posts:Required Fields
| Field Name | Field Type | Slug | Notes |
|---|---|---|---|
| Name | Plain Text | name | Article title |
| Slug | Plain Text | slug | URL slug |
| Post Body | Rich Text | post-body | Main content |
| Post Summary | Plain Text | post-summary | Excerpt |
Optional Fields
| Field Name | Field Type | Slug | Notes |
|---|---|---|---|
| Main Image | Image | main-image | Featured image |
| Publish Date | Date | publish-date | Publication date |
| Categories | Multi-Reference | categories | Link to Categories collection |
| Tags | Multi-Reference | tags | Link to Tags collection |
| Author | Reference | author | Link to Authors collection |
Content Formatting
Skayle converts BlockNote JSON to minified HTML optimized for Webflow’s Rich Text fields.Why Minified HTML?
Webflow’s CMS editor interprets newlines between tags as line breaks, which can cause rendering issues (especially with lists). Skayle minifies HTML to prevent this:Supported Elements
| BlockNote Type | HTML Output |
|---|---|
| Paragraph | <p> |
| Heading 1-6 | <h1> - <h6> |
| Bullet List | <ul><li> |
| Numbered List | <ol><li> |
| Blockquote | <blockquote> |
| Code Block | <pre><code> |
| Image | <img> |
| Link | <a> |
| Bold | <strong> |
| Italic | <em> |
Webflow Rich Text fields have specific HTML requirements. Skayle automatically formats content to be compatible.
Taxonomy Mapping
Multi-Reference Fields
Webflow uses multi-reference fields for many-to-many relationships:- Create separate collections for Categories and Tags
- Add multi-reference fields to your Posts collection
- Configure the field slugs in Skayle
Syncing Process
- Import from Webflow
- Export to Webflow
Fetches items from your taxonomy collections:Creates Skayle taxonomies and stores mappings.
Image Handling
Webflow requires images to be hosted externally or uploaded to their CDN:External URLs
For image fields, provide the full URL:Webflow Assets
For better performance, consider uploading to Webflow’s asset manager first.Publishing Workflow
Draft vs Published
Webflow items can be in draft or published state:- Draft: Item exists but isn’t live on the site
- Published: Item is live and visible
- Use Webflow’s publish feature
- Or configure auto-publish in your workflow
Staging vs Production
Webflow has staging and production environments:- CMS changes go to staging first
- Publishing the site pushes changes to production
After Skayle publishes content, you may need to publish your Webflow site to make changes live.
Troubleshooting
Connection Issues
401 Unauthorized
401 Unauthorized
404 Not Found
404 Not Found
- Verify Site ID is correct
- Check Collection ID exists
- Ensure collection is in the correct site
Rate Limited
Rate Limited
- Webflow has API rate limits
- Wait and retry
- Consider batching requests
Publishing Issues
Field validation errors
Field validation errors
- Check field slugs match exactly
- Verify required fields are mapped
- Ensure field types are compatible
Rich Text not rendering
Rich Text not rendering
- Check HTML is properly formatted
- Verify no unsupported tags
- Test with simple content first
References not working
References not working
- Ensure taxonomy collections exist
- Run taxonomy sync first
- Verify reference field configuration
API Rate Limits
Webflow enforces API rate limits:| Plan | Requests/Minute |
|---|---|
| Starter | 60 |
| CMS | 120 |
| Business | 120 |
| Enterprise | Custom |
Best Practices
- Test field mapping: Verify all fields work before bulk publishing
- Use staging: Test content in staging before publishing to production
- Sync taxonomies first: Always sync categories/tags before articles
- Monitor rate limits: Don’t publish too many articles at once
- Backup collections: Export your CMS data regularly