CMS

Strapi

Strapi is an open-source headless CMS you run yourself: content-types hold entries, and a REST API over them is what everything else talks to.

Authentication

  • API token

Actions

Generic API request. Call any Strapi API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Create entryCreate an entry in a Strapi content-type (POST {collection}).
  • Delete entryDestructiveDelete an entry from a Strapi content-type (DELETE {collection}/{documentId}).
  • Get current userRetrieve the authenticated user tied to the API token (GET users/me, users-permissions plugin).
  • Get entryRetrieve a single Strapi entry by its documentId (GET {collection}/{documentId}), with optional populate.
  • Get userRead one users-permissions user by numeric id - username, email and the confirmed / blocked flags that decide whether they can actually sign in.
  • List entriesList entries of a Strapi content-type (GET {collection}), with optional pagination, sort and populate.
  • List usersList users (GET users, users-permissions plugin).
  • Update entryDestructiveUpdate an entry in a Strapi content-type (PUT {collection}/{documentId}).

Triggers

  • Entry created or updated (webhook)Starts when the connected Strapi instance delivers an entry.create or entry.update webhook event for any content-type collection.
  • New or updated entryStarts when an entry in the selected Strapi content-type collection is created or updated, so a workflow can react to content changes.
  • New or updated userStarts when a Strapi users-permissions user is created or updated, detected by its updatedAt timestamp advancing past the stored cursor on each poll.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.