title: "CMS Integrations Overview" description: "Learn about all CMS platforms iContentForge supports, how to choose the right connector, and the universal four-step connection process." section: "CMS Integrations"
CMS Integrations Overview
iContentForge connects directly to your content management system (CMS) to automate publishing of AI-generated articles, eliminating manual copy-pasting and letting you manage your entire content pipeline from one dashboard.
Supported Platforms
iContentForge offers native connectors for the most popular publishing platforms:
| CMS Platform | Best For | Connection Method |
|---|---|---|
| WordPress | General blogging, business websites | REST API + Application Password |
| Ghost | Newsletters, subscription blogs | Admin API Key |
| Shopify | E-commerce store blogs | Admin API Token |
| Webflow | Designer-led websites | Site API Key |
| Strapi | Headless CMS (self-hosted) | API Token |
| Contentful | Headless CMS (cloud) | Management API Key |
| Sanity | Structured content / headless | Project ID + API Token |
| Medium | Cross-posting to a built-in audience | Integration Token |
| Substack | Email newsletters | API access |
For platforms not listed above including Wix, Squarespace, custom backends, NestJS/Express apps, or any service with a REST endpoint use the Generic Webhook connector.
The Generic Webhook is the most flexible option. It sends a signed JSON payload to any HTTPS endpoint you control, letting you handle the publish logic yourself in any language or framework. See the full guide: Generic Webhook Integration
You can create multiple Projects in iContentForge, each connected to a different CMS. For example, a WordPress business blog and a Shopify store blog can both be managed from a single iContentForge account just set up separate Projects.
How to Choose Your Connector
| Your setup | Recommended connector |
|---|---|
| Standard blog or business site | WordPress |
| Newsletter or paid subscription | Ghost or Substack |
| E-commerce store blog | Shopify |
| Developer / custom backend (Node.js, Python, etc.) | Generic Webhook |
| Headless CMS | Strapi, Contentful, or Sanity |
| Cross-posting to reach a wider audience | Medium |
| Any platform not listed above | Generic Webhook |
Universal Connection Process
All connectors follow the same four steps in your Project Settings.
1. Select Connector Type
Navigate to Project Settings CMS Integration. Click "Connect a CMS" and select your platform from the dropdown list.
2. Enter Connection Credentials
Each CMS requires specific credentials. The form updates to show exactly the fields needed for your chosen platform. Common fields include:
- API Endpoint / Base URL your site's API address
- API Key / Application Password / Token your authentication credential
- Secret Key for Webhook, used to sign and verify payloads
Keep API credentials secure. iContentForge uses them only to send articles and never exposes them in the frontend. You can regenerate credentials from your CMS admin panel at any time.
3. Test the Connection
Click "Test Connection". iContentForge makes an API call to your CMS to verify credentials and permissions. A success message confirms you're ready.
4. Save the Configuration
Click "Save Connector". The connection is now active. All articles set to publish in this project will be automatically sent to this CMS according to your Drip Feed schedule.
Connector Labels
When saving a connector, give it a descriptive Label (e.g., "Main Company Blog", "Client XYZ Ghost"). This is your internal reference and is not sent to the CMS.
Project Binding
A CMS connector is saved at the Project level:
- All articles in a project publish to its connected CMS.
- To publish to two different platforms, create two separate Projects.
- Connector settings are managed independently per Project.
Changing the CMS connector for an existing Project affects all future publish attempts. Articles already in "Published" status are not moved or altered.
Next Steps
- Set up a specific platform:
- Configure automatic publishing: Drip Feed
- Manage your content queue: Publish Hub