ActionContentfulUpdated September 2026
How do I query Contentful entries?
Short answer: You can get entries in Contentful by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Contentful Get Entries action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 |
Sample request
{"content_type": "e.g. blogPost","limit": "100","skip": "0","order": "e.g. -sys.createdAt","query": "e.g. release notes"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Get Entries.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Entries.
What does the Get Entries action do in Contentful?
Returns paginated entries with Contentful's query syntax — content_type, field filters, full-text search, locale. Use include parameter to resolve referenced entries inline. The base read action for fetching content into downstream systems.
What inputs does Get Entries require?
Get Entries has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Contentful returns an error?
The run history shows the failed step with its input and the error message Contentful returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Entries support batch operations?
Run Get Entries inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Contentful's rate limits.
More actions
Other Contentful actions.
Action
Get Entry
Returns a single entry by ID with full content and optional include parameter to resolve linked entries inline. Useful for "render this specific blog post" or "fetch the homepage banner content" workflows.
ActionList Content Types
Returns every content type in the space with field definitions. Useful for validating content shape at workflow-build time and for introspection workflows that adapt to schema changes.
ActionSearch Entries
Full-text search across entries with Contentful's match-style filter syntax (fields.title[match]="query"). For RAG-style "ground answer in our CMS content" agentic workflows.