Summary

The Entity Query node supports custom conditions that allow filtering entities by any field with configurable operators. This enables complex queries that go beyond the built-in filters.

Business Value

  • Enables precise targeting of specific content subsets
  • Supports complex filtering logic with multiple conditions
  • Provides flexibility for custom field filtering
  • Reduces need for post-query filtering in workflows

Condition Structure

Each condition is an object with:

  • field: The field name to filter on
  • value: The value to compare against
  • operator: Comparison operator (defaults to "=")

Supported Operators

  • =: Equals
  • <>: Not equals
  • >: Greater than
  • >=: Greater than or equal
  • <: Less than
  • <=: Less than or equal
  • IN: Value in array
  • NOT IN: Value not in array
  • CONTAINS: String contains
  • STARTS_WITH: String starts with
  • ENDS_WITH: String ends with

Example Use Cases

  • Find all articles by a specific author
  • Query products within a price range
  • Filter content by custom taxonomy field
  • Find entities with specific status values

Comments

joevagyok created an issue. See original summary.

gxleano’s picture

gxleano commented

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

d34dman’s picture

d34dman commented
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.