Manage Strapi CMS v5 content types via webhook using HTTP requests

n8n workflow template: Strapi CMS v5 content API An importable n8n workflow that creates, updates, and lists entries on Strapi v5 through a single webhook. It talks to Strapi’s REST API with HTTP Request nodes and a Strapi Token API credential, so it stays compatible with v5 even though n8n’s built-in Strapi node targets older Strapi versions. What’s in this repo | File | Purpose | |------|---------| | strapi-v5-content-n8n-workflow.json(./strapi-v5-content-n8n-workflow.json) | Workflow export — use for Import from File / Import from URL in n8n or when submitting to the n8n template gallery | Features - One webhook, three actions — actiontype routes to create, update, or getall. - Any content type — pass the plural API ID (contenttypeplural) per request; no workflow fork per collection. - Strapi v5 — uses documentId on update and REST URLs shaped for the v5 API. - List with options — getall supports status, pagesize, pagenumber, and populate= in the workflow. - Clear failures — checks Strapi error responses and can mark the execution failed via Stop and Error. - Extra documentation — after import, open the large sticky note on the canvas for full payload examples and security notes. Requirements - n8n (self-hosted or cloud) - Strapi v5 with a valid API token (Settings → API Tokens) and permissions for the collections you automate Quick start 1. In n8n, choose Import workflow → From File and select strapi-v5-content-n8n-workflow.json (or import from this repo’s raw URL). 2. Create a Strapi Token API credential in n8n and attach it to all HTTP Request nodes (Create, Update, Get all). 3. Activate the workflow and copy the webhook’s Production URL (default path segment: strapi-v5-content). Change the path in the Webhook node if it clashes with another active workflow on the same instance. 4. Send POST requests with a JSON body as below. Do not include a trailing slash on strapibaseurl. Webhook security (recommended before production) The template ships with no webhook authentication so you can test quickly. Before exposing the URL publicly, add authentication on the Webhook node (for example Header Auth with X-API-Key and a long random secret) and send that header on every call. The workflow intentionally does not hardcode your Strapi host: callers supply strapibaseurl in the body, so only trusted clients should be allowed. Request body reference All actions expect a JSON object (typically the webhook body). Common fields: | Field | Required | Description | |-------|----------|-------------| | actiontype | Yes | "create" \| "update" \| "getall" | | strapibaseurl | Yes | Strapi origin, no trailing slash (e.g. https://your-project.strapiapp.com) | | contenttypeplural | Yes | Plural API ID from Content-Type Builder (e.g. articles) | getall Optional: status (published / draft), pagesize, pagenumber. create Required: data — object of field names and values matching your Strapi schema. update Required: documentId (Strapi v5), and data with fields to patch. Example shapes: json { "actiontype": "getall", "strapibaseurl": "https://your-strapi.example.com", "contenttypeplural": "articles", "status": "published", "pagesize": 10, "pagenumber": 1 } json { "actiontype": "create", "strapibaseurl": "https://your-strapi.example.com", "contenttypeplural": "articles", "data": { "title": "Hello", "slug": "hello" } } json { "actiontype": "update", "strapibaseurl": "https://your-strapi.example.com", "contenttypeplural": "articles", "documentId": "<from getall or Strapi admin>", "data": { "title": "Updated title" } } For full parameter notes, pagination examples, and MCP / AI agent usage, see the sticky note inside the imported workflow. License This project is released under the MIT License(./LICENSE) (Copyright © 2026 IBSolutions.dev).