title: "Webflow Integration" description: "Connect iContentForge to Webflow using the V2 API. Learn how to get your API Key, Collection ID, and configure field names for automated publishing." section: "CMS Integrations"

Webflow Integration

iContentForge seamlessly connects to your Webflow site, allowing you to automatically publish AI-generated articles directly to a specified CMS Collection. This guide walks you through setting up the connection and configuring the field name mapping.

Prerequisites

Before you begin, ensure you have:

An active iContentForge project with articles in the Ready status.
A Webflow site with at least one CMS Collection set up for blog posts or articles.
Admin or Owner access to the Webflow site to generate API credentials.

Step 1: Generate a Webflow API Key

iContentForge uses Webflow's V2 API for authentication. You need to generate a unique API key from your Webflow dashboard.

Log in to your Webflow Dashboard.
Select the site you want to connect.
Go to Project Settings > Integrations > API Access.
In the "API Access" section, click Generate API Key.
Give the key a descriptive name (e.g., "iContentForge Auto-Publish").
Select the permissions: You must grant Read and Write access for CMS.
Click Generate Key and Copy the key immediately. Store it securely, as you will not be able to see it again.

鈿狅笍

Security Note: Your Webflow API key grants write access to your CMS. Treat it like a password. Never share it publicly or commit it to version control. You can regenerate or revoke it at any time from the same Webflow settings panel.

Step 2: Find Your Collection ID

Next, you need the unique ID of the CMS Collection where articles should be published.

In your Webflow Designer, open the CMS panel.
Select the target Collection (e.g., "Blog Posts").
Look at the URL in your browser's address bar. The Collection ID is the alphanumeric string after /collection/.
```
https://webflow.com/design/YOUR-SITE-NAME#/cms/YOUR-SITE-ID/collection/COLLECTION-ID
```
Copy the COLLECTION-ID.

Step 3: Find Your Collection Field Slugs

This step is critical. Webflow CMS field names (slugs) are defined by you when building your Collection. They are not standardized across sites a field that stores article body content might be called post-body, content, body, article-content, or anything else depending on how you built your Collection.

You must tell iContentForge the exact slug name for each field.

To find your field slugs:

In the Webflow Designer, open the CMS panel and select your target Collection.
Click Settings (gear icon) on the Collection.
For each field, note the Field Name shown under the field label this is the slug used in the API (e.g., post-body, main-image, meta-title).

Step 4: Connect in iContentForge

With your API Key, Collection ID, and field slugs ready, you can now set up the connection.

Navigate to your Project in iContentForge and go to Settings > CMS Integration.
Select Webflow from the list of CMS providers.
Enter the required credentials:
- API Key: Paste the Webflow V2 API Key you copied.
- Collection ID: Paste the Collection ID.
Fill in the Field Name Configuration section with the actual slug names from your Webflow Collection:

iContentForge Configuration Field	Description	Your Collection's Default (example)
Body Field Slug	The field that stores the article's HTML body content.	`post-body`
Summary Field Slug	The field for the article excerpt/summary.	`post-summary`
SEO Title Field Slug	The field for the SEO meta title.	`meta-title`
SEO Description Field Slug	The field for the SEO meta description.	`meta-description`
Cover Image Field Slug	The field for the featured/cover image URL.	`main-image`

馃挕

Leave a field blank to use the default value shown above. Only override a field if your Webflow Collection uses a different slug name. Most issues with Webflow publishing are caused by field name mismatches double-check your slugs in the Webflow Collection settings if content isn't appearing.

Click Test Connection. A success message confirms iContentForge can communicate with your Webflow CMS.
Click Save & Configure.

How Publishing Works

Once connected and configured:

Articles in the Ready status will be published according to your project's Drip Feed schedule (approximately every 5 minutes).
iContentForge sends the article data to the Webflow API, creating a new item in your mapped Collection.
The article status in iContentForge will change from Ready to Published.
The new item will be in Draft mode within your Webflow CMS. You can review it, add final touches (like a custom thumbnail), and publish it to your live site when ready.

鈩癸笍

Note: iContentForge pushes content to the Webflow CMS as draft items. You must log into Webflow to publish them to your live site. This provides a final quality control checkpoint.

Troubleshooting

"Invalid API Key" Error: Regenerate your API key in Webflow and update it in iContentForge. Ensure you selected CMS Read/Write permissions.
"Collection Not Found" Error: Verify the Collection ID is correct. The ID is case-sensitive.
Content Not Appearing / Empty Fields: The most common cause is a field slug mismatch. Go back to Step 3 and verify your Webflow Collection field slugs, then update the Field Name Configuration in iContentForge.
HTML Formatting Issues: Ensure the body field in your Webflow Collection is configured as a Rich Text field, not a Plain Text field.
Images Not Appearing: The Cover Image field must store an image URL. Ensure the field type in Webflow is compatible (e.g., Image or Plain Text URL). The URL must be publicly accessible.

Next Steps

Learn how to automate your publishing schedule with Drip Feed.
Understand the complete Article Generation Workflow.
Explore other available CMS Integrations.

Untitled