Search flow cards

Runs a card search within a single flow, using a condition language that supports nested filter trees and aggregations over collections.

This endpoint should not be confused with saved filters (/v1/flows/{id}/filters): those persist a reusable view configuration, while this one runs a one-off query and returns the matching cards directly.

The request is not paginated — the page and pageSize fields are not accepted and return a 400 error if present in the body. The envelope requires order, orderBy, fields (the path projection returned per card) and conditions, the latter being a non-empty list of condition nodes.

Each condition node is either a group (with logic and a list of subconditions) or a leaf (with a field path and, optionally, a comparison operator and value); in both cases the scope field — any, all or sum — is required and defines the aggregation semantics over collections.

Valid paths for orderBy, fields and conditions depend on the flow's field catalog. Using an incompatible path or operator may not be rejected by the envelope's initial validation and can result in an internal server error instead of a friendly validation message — we recommend checking the available paths for the flow beforehand.

Note that, unlike saved filters, the flow parameter in this path is {flowId}, not {id}.

application/json

List of cards from the flow that match the given conditions, projected by the paths indicated in fields and sorted according to order/orderBy.

Bodyapplication/json

curl --location '/v1/filters/flows//search' \ --header 'Content-Type: application/json' \ --data '{ "order": "asc", "orderBy": "card.enteredCurrentPhaseAt", "fields": [ { "path": "card.title" }, { "path": "card.value" } ], "conditions": [ { "scope": "any", "path": "card.value", "operator": "gte", "value": 0 } ] }'

Search flow cards

Requisição

Respostas