Short answer: Drop the "Strapi → List Strapi Entries" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Content Type (plural) content_type | string | Required | Content Type (plural). Example: articles |
Sort sort | string | Optional | Field and direction |
Page pagination_page | string | Optional | Page. e.g. "1" |
Page Size pagination_pageSize | string | Optional | Page Size. e.g. "25" |
Filters (query string) filters | string | Optional | Strapi filter query params, e.g. 'filters[status][$eq]=published' |
{"content_type": "e.g. articles","sort": "e.g. createdAt:desc","pagination_page": "1","pagination_pageSize": "25","filters": "e.g. filters[status][$eq]=published"}
{"data": [{"id": 1,"attributes": {"title": "Article 1"}}],"meta": {"pagination": {"page": 1,"total": 42,"pageSize": 25}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.