STRAPI n8n INTEGRATION: AUTOMATE STRAPI WITH N8N

The Create Entry action allows you to programmatically add new content records to any Strapi content type directly from your n8n workflows. This is your go-to action whenever external events should result in new content being added to your CMS—whether that's a new product launch, a user registration, or content imported from another platform.

Key parameters: The Credential to connect with is a required dropdown to select your authenticated Strapi account. This establishes the secure connection to your Strapi instance. Resource is a required dropdown set to "Entry" to indicate you're working with content entries. Operation is a required dropdown set to "Create" for this action. Content Type is a required text field where you specify the API ID of your content type (e.g., "articles", "products", "blog-posts"). This must match exactly the API name configured in Strapi. Columns is an optional text field accepting a comma-separated list of fields (e.g., "id,name,description") to control which columns appear in the output data.

Use cases: Automatically create blog post entries when content is approved in your editorial workflow tool. Generate product entries in Strapi whenever new SKUs are added to your inventory management system. Create user profile entries when new accounts are registered through your authentication provider.

The Get Many Entry action retrieves multiple records from a specified Strapi content type in a single operation. This is essential for batch processing scenarios, data synchronization workflows, or any automation that needs to work with collections of content rather than individual items.

Key parameters: Credential to connect with is a required dropdown for selecting your Strapi account credentials for authentication. Resource is a required dropdown set to "Entry" to target content entries. Operation is a required dropdown configured as "Get Many" to retrieve multiple records. Content Type is a required text field specifying which content type to query (e.g., "articles", "products"). Return All is an optional toggle switch that, when enabled, fetches every available entry, overriding the Limit parameter. Useful for complete data exports but use cautiously with large datasets. Limit is an optional number field (default: 50) that caps how many entries are returned. Only applies when "Return All" is disabled. Options is an expandable section for adding additional query parameters like filters, sorting, or field selection.

Use cases: Export all published articles to a static site generator for deployment. Sync product catalogs from Strapi to external marketplaces on a scheduled basis. Retrieve user entries for batch email campaigns using tools like Brevo or data analysis workflows.

The Get Entry action fetches a single, specific record from your Strapi content type using its unique identifier. This targeted retrieval is perfect for workflows that need to look up particular items, verify content existence, or retrieve full details about a specific entry before performing subsequent operations.

Key parameters: Credential to connect with is a required dropdown to select the Strapi account credential that authenticates your connection. Resource is a required dropdown set to "Entry" indicating the action targets content entries. Operation is a required dropdown configured as "Get" for single-entry retrieval. Content Type is a required text field where you specify the exact content type API ID (e.g., "articles", "products") containing the entry. Entry ID is an optional text field accepting the unique identifier of the specific entry to retrieve. Supports both fixed values and dynamic expressions for flexible workflows.

Use cases: Verify that a specific product entry exists before attempting an update operation. Retrieve full article details when a webhook notifies you of a comment on that article. Look up user profile data when processing a support ticket referencing that user's ID.

The Update Entry action modifies existing content records in your Strapi content types. This is crucial for keeping your CMS data current—whether you're syncing changes from external systems, updating status fields based on workflow events, or maintaining real-time data accuracy across your connected applications.

Key parameters: Credential to connect with is a required dropdown for selecting your authenticated Strapi account connection. Resource is a required dropdown set to "Entry" to indicate operations on content entries. Operation is a required dropdown configured as "Update" to modify existing records. Content Type is a required text field specifying the API ID of the content type (e.g., "products", "articles") containing the entry to update. Update Key is a required text field identifying which field to use for locating the entry. Typically set to "id" for matching by unique identifier, but can be configured for other unique fields. Columns is a required text field containing a comma-separated list of fields to update (e.g., "id,name,description"). Only the specified columns will be modified.

Use cases: Automatically update product prices when your pricing engine calculates new values. Change article status from "draft" to "published" when an editor approves content. Sync customer profile updates from your HubSpot CRM back to corresponding Strapi entries.

💡 TIP: When configuring the Columns parameter, always include the field used as your Update Key (typically "id") along with the fields you want to modify. This ensures n8n can properly match and update the correct entry.

The Delete Entry action permanently removes content records from your Strapi content types. Use this action carefully—it's designed for maintaining data hygiene by removing obsolete, duplicate, or invalidated entries as part of your automated content lifecycle management.

Key parameters: Credential to connect with is a required dropdown to select the Strapi account credential for authentication. Resource is a required dropdown set to "Entry" to target content entries. Operation is a required dropdown configured as "Delete" for removal operations. Content Type is a required text field where you enter the API ID of the content type (e.g., "article", "product") containing the entry to remove. Entry ID is a required text field specifying the unique identifier of the entry to delete. Supports both fixed values and expression mode for dynamic ID generation within workflows.

Use cases: Automatically remove product entries when items are discontinued in your inventory system. Delete temporary or test content entries after a specified retention period. Clean up duplicate entries identified by a data quality check workflow, similar to how you might merge duplicate companies in HubSpot.