Manage Strapi CMS v5 content types via webhook using HTTP requests

n8n workflow template: Strapi CMS v5 content API

An importable [n8n](https://n8n.io/) 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