Managing CMS Connections
The CMS Connections dashboard is your central hub for managing all the content management systems you've integrated with your iContentForge project. From here, you can view connection statuses, update credentials, and configure publishing destinations.
You can access this area by navigating to your project dashboard and clicking Settings > CMS Connections.
The CMS Connections dashboard showing a list of connected platforms and their status
Viewing Your Connected Platforms
The main connections table provides an overview of all your integrations.
| Column | Description |
|---|---|
| Connector Name | The custom label you gave this connection (e.g., "Main Blog," "Client Store"). |
| Platform Type | The CMS platform (WordPress, Ghost, Shopify, etc.). |
| Connection Status | Connected, Error, or Checking.... A green check indicates a successful health check. |
| Last Used | The timestamp of the last successful article publish or test. |
| Actions | Options to Edit, Test, or Delete the connection. |
The connection status is determined by an automatic health check that runs periodically and when you visit the page. A status of Error means the last API test failed, likely due to invalid credentials or a network issue.
Editing a CMS Connection
To update the credentials or settings for an existing connection:
- Click the Edit (pencil) icon in the Actions column.
- A configuration modal will open, pre-filled with the current settings.
- Update the necessary fields:
- Connector Name: Change the friendly name for this connection.
- API Credentials: Update the API URL, Key, or Token. For security, existing passwords are masked.
- Default Category/Tag: Change the default category, tag, or collection where articles will be published if one isn't specified during article generation.
- Click Save & Test. iContentForge will immediately validate the new credentials.
Always use the Save & Test button after editing. This ensures your new credentials are valid before you attempt to publish articles, preventing failed publish jobs.
Deleting a Connector
If you no longer need a CMS connection:
- Click the Delete (trash) icon in the Actions column.
- Confirm the action in the pop-up dialog.
Deleting a connection is permanent and cannot be undone. Any articles in the scheduled or queued state for this CMS will fail to publish. It's recommended to pause or complete any pending publishing queues before deletion.
Using Multiple CMS Connectors
A single iContentForge project can be connected to multiple CMS instances. This is useful for:
- Content Syndication: Publishing the same generated article to a primary blog and a secondary platform like Medium or Substack.
- Client Management: Managing separate WordPress sites for different clients from one central iContentForge agency account.
- Separate Content Types: Sending product-focused articles to a Shopify blog and informational guides to a main WordPress site.
When generating articles, you can select which CMS connection(s) to publish to in the Publish Settings step.
Connection Health Check
iContentForge performs automatic health checks to ensure your connections are active. You can also trigger a manual test:
- Click the Test (play) icon in the Actions column for any connection.
- The status will temporarily change to
Checking.... - A success or error notification will appear, and the Connection Status and Last Used columns will update accordingly.
A failed health check typically indicates:
- An incorrect or expired API key/token.
- A change in the CMS API URL.
- Network or firewall restrictions blocking iContentForge's servers.
- Temporary downtime of your CMS platform.
Next Steps
- Learn how to set up a specific platform: WordPress Integration
- Configure automatic publishing schedules: Using Drip Feed
- Understand the article publishing lifecycle: Article Statuses