Short answer: Drop the "Contentful → Get 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 ID content_type | string | Optional | Filter entries by content type |
Limit limit | string | Optional | Max entries (max 1000) |
Skip skip | string | Optional | Number of entries to skip (pagination) |
Order order | string | Optional | Field to order by (prefix with - for descending) |
Full-Text Search query | string | Optional | Search across all text fields |
{"content_type": "e.g. blogPost","limit": "100","skip": "0","order": "e.g. -sys.createdAt","query": "e.g. release notes"}
{"skip": 0,"items": [{"sys": {"id": "entry123","type": "Entry","contentType": {"sys": {"id": "blogPost"}}},"fields": {"body": "Content here","title": "Hello World"}}],"limit": 100,"total": 42}
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.