DatoCMS icon

DatoCMS

Interact with DatoCMS API

Overview

This node interacts with the DatoCMS API to retrieve multiple records of a specified item type. The "Get Many" operation under the "Record" resource allows users to fetch a list of records, optionally filtered by field values, and control the amount and detail of data returned.

Common scenarios where this node is beneficial include:

  • Fetching a batch of content entries (e.g., blog posts, products) from DatoCMS for further processing or integration.
  • Retrieving records that meet specific criteria, such as all published articles in a certain category.
  • Importing or syncing data from DatoCMS into other systems or workflows.

Practical example:

  • A marketing automation workflow that pulls all product records with stock greater than zero to send promotional emails.
  • A reporting workflow that gathers all records updated within the last week for analytics.

Properties

Name Meaning
Item Type The type of item (content model) to retrieve records from. Can be selected from a searchable list or specified by ID.
Filters One or more filters to narrow down the records by field values. Each filter includes:
- Field Name or ID: The field to filter on.
- Operator: Comparison operator (Equals, Exists, Greater Than, In, etc.).
- Value: The value to compare against (not required for "Exists").
Return All Whether to return all matching records or limit the number of results.
Limit Maximum number of records to return if "Return All" is false. Minimum 1, default 50.
Nested Whether to include nested data for related records. When enabled, referenced records are included as full objects instead of just their IDs.

Output

The output JSON contains either:

  • An array of record objects when returning multiple records. Each record includes its fields and metadata as provided by DatoCMS.
  • If filters are applied, only records matching those filters are included.
  • Pagination details are handled internally; if "Return All" is true, all matching records are fetched via pagination.

No binary data is output by this operation.

Dependencies

  • Requires an API authentication token credential for DatoCMS.
  • Uses the official DatoCMS Node.js client library to communicate with the API.
  • No additional environment variables are needed beyond the API token and optional environment name.

Troubleshooting

  • No records returned: Check that the correct item type is selected and that filters are correctly configured. Ensure the API token has access to the requested item type.
  • Limit ignored or too many results: If "Return All" is false but many records are returned, verify the "Limit" property is set properly. Note that enabling "Nested" may reduce the maximum allowed limit to 30.
  • API errors: Errors from the DatoCMS API (e.g., permission issues, invalid item type ID) will be surfaced as node execution errors. Verify API credentials and permissions.
  • Filter syntax errors: Ensure filter operators and values are valid. For "In" and "Not In" operators, use comma-separated values without extra spaces.

Links and References

Discussion