DSL Condition
Evaluate a DSL query and check if a ticket matches.
Tests a ticket against a DSL query, or filters a list of tickets.
Dynamic ports
A resolver decides this node's ports at run time. The ticket input widens to a list when a list of tickets is connected, and the node then exposes an interpolation arg for each ${ArgA}, ${ArgB}, … placeholder used in the query, adding one empty arg slot at a time. The outputs also change with the input: a single ticket yields a boolean result, while a list yields the filtered tickets plus a count.
Inputs
- Ticketrequired — Ticket. Uses the ticket as the document that the DSL query is evaluated against. The node feeds that ticket into the query engine and returns whether the expression matches it.
- ArgArepeats — String. Provides the first interpolation argument referenced by the query as ${ArgA}. The node exposes ArgA, ArgB, and later slots one at a time as earlier args are wired.
Outputs
- Result — Boolean. Represents the match result for the supplied ticket. True means the ticket satisfies the DSL query, and false means it does not.
Configuration
- Query — DSL query. Controls the DSL expression that is evaluated against the incoming ticket. The query can use the same filtering syntax documented for search, including field comparisons, logical operators, presence checks, references, and other query clauses that are valid in ticket search.
Example use cases
Gate an automation
Continue only when the ticket matches your query.
dsl
priority = "High" and assignee = @meFilter a list
Pass a list of tickets to narrow it to the ones that match before acting on them.