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 IDuuid: Entity UUIDlabel: Entity label/titlebundle: 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
- Entity Query node queries articles modified in last 24 hours
- ForEach loop iterates over results array
- Inside loop: process, transform, or validate each entity
- Entity Save node persists changes
Comments
Comment #2
gxleano commentedI have contributed (not only by code, but discussion, presentation, testing or anything related).
Comment #3
d34dman commented