Summary

The Entity Query node's output is optimized for use with the ForEach loop node, enabling efficient batch processing of query results.

Business Value

  • Enables batch processing workflows with minimal configuration
  • Provides consistent data structure for iteration
  • Supports both lightweight (IDs only) and full entity processing
  • Optimizes memory usage for large result sets

Results Array Structure

Each item in the results array contains:

  • id: Entity ID
  • uuid: Entity UUID
  • label: Entity label/title
  • bundle: Entity bundle (content type)
  • entity_type: Entity type (when load_entities=false)
  • entity: Full serialized entity (when load_entities=true)

Processing Patterns

  • Lightweight: Query IDs only, load entities individually in loop for memory efficiency
  • Bulk: Load all entities upfront for faster processing of smaller sets
  • Paginated: Use offset/limit with has_more flag for processing large datasets

Example Workflow Pattern

  1. Entity Query node queries articles modified in last 24 hours
  2. ForEach loop iterates over results array
  3. Inside loop: process, transform, or validate each entity
  4. Entity Save node persists changes

Comments

joevagyok created an issue. See original summary.

gxleano’s picture

I have contributed (not only by code, but discussion, presentation, testing or anything related).

d34dman’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.