Strapi Integration

Connect your iContentForge project to a Strapi CMS (self-hosted or Strapi Cloud) to automatically publish generated articles. This guide covers the required API token permissions, base URL configuration, and content type mapping.

Prerequisites

Before you begin, ensure you have:

• An active iContentForge project with articles in Ready status.
• Admin access to your Strapi dashboard to create an API token.
• Your Strapi instance must be accessible via a public URL (for iContentForge's servers to connect).

Step 1: Generate a Strapi API Token

You need a Strapi API Token with the correct permissions to allow iContentForge to create articles.

1. Log in to your Strapi admin panel.
2. Navigate to Settings → API Tokens (under Global Settings).
3. Click Create new API Token.
4. Configure the token as follows:
   • Name: e.g., iContentForge Publishing
   • Token type: Select Full-access for simplicity, or create a Custom type with the specific permissions listed below.
   • Description: (Optional) Note that this token is for automated article publishing.

5. Click Save. Copy the generated token immediately—you will not be able to see it again.

Step 2: Configure the Connector in iContentForge

1. In your iContentForge dashboard, go to your Project.

2. Navigate to the CMS Integrations tab.

3. Click Add New Connector and select Strapi from the list.

4. Fill in the connection details:

   • Connection Name: A friendly name for this connection (e.g., "Company Blog").
   • Base URL: The full URL to your Strapi instance, including the /api path.
     • Strapi Cloud Example: https://your-project.strapiapp.com/api
     • Self-hosted Example: https://strapi.yourdomain.com/api
   • API Token: Paste the token you copied from Strapi.

5. Click Test Connection. A success message confirms iContentForge can communicate with your Strapi instance.
6. Click Save Connector.

Step 3: Map Content Types and Fields

After a successful connection, you must map iContentForge's article data to your Strapi Content-Type fields.

1. In the Strapi connector settings, find the Content Type Mapping section.
2. Select your target Content-Type from the dropdown (e.g., article).
3. Map the required fields. At a minimum, you should map:
   • Title: Map to your Strapi field for the article title (e.g., Title).
   • Content (HTML): Map to your Strapi field that accepts rich text/HTML (e.g., Content or Body).

4. You can optionally map other iContentForge data:

   • Featured Image URL: Map to a media field.
   • Meta Description: Map to a text field.
   • Slug: Map to a UID field.
   • Author: Map to a relation field (requires advanced setup).
   • Tags/Categories: Map to relation fields.

5. Configure the Default Article Status in Strapi. Choose whether articles should be created as Draft or published immediately (Published).

6. Click Save Configuration.

How Publishing Works

Once configured, articles will be published according to your project's Drip Feed schedule (approximately every 5 minutes).

1. An article in Ready status is queued for publishing.
2. iContentForge sends a POST request to your Strapi API endpoint (/api/[content-type-plural]) with the mapped data.
3. The article is created in Strapi with the status you configured.
4. In iContentForge, the article status updates to Published.
5. If an error occurs (e.g., invalid token, field mismatch), the status changes to Error, and you can check the logs for details.

Troubleshooting

Next Steps

Your Strapi integration is now complete. Articles will be published automatically based on your schedule.

• Learn how to control the publishing pace with Drip Feed Scheduling.
• Review the status of all your articles in the Project Dashboard.
• Explore other supported CMS Integrations.