Content Query action
Resolves a query, or a saved work stream, to a list of content—so a flow can run across a whole set of assets instead of reacting to one event. In the action picker it is Content Query, under Integration Actions. Wire its results output into a loop to process every match.
It only reads, so it runs unchanged under a dry run—a dry run always previews the real result set and count.
Fields
| Field | Required | Description |
|---|---|---|
| Connection | Yes | The Brightspot connection to query. |
| Source | Yes | Where the list comes from—Custom Query or Work Stream. |
Custom Query
Builds the list from a content type and optional filters.
| Field | Required | Description |
|---|---|---|
| Site | No | Restrict the query to one site. Defaults to the connection's site when it pins exactly one, otherwise every accessible site. |
| Content Type | Yes | The type of content to query. |
| Predicate | No | How to narrow the type—Match Fields or Query Expression. Leave it unset to match every item of the type. |
| Max Results | No | Caps how many items are returned and iterated. Defaults to 100; the CMS caps it at 1000. |
Match Fields builds the filter from conditions in the editor:
- Match—how to combine the conditions: All, Any, or None.
- Conditions—a list of Condition clauses (Field, Operator, Value) and nested Groups, each with its own Match and conditions, so you can express one condition and either of two others. A condition's value accepts variables.
Query Expression is a raw query, for filters the builder cannot express—an operator outside the allowed set, or and, or, and not combined with grouping:
| Field | Required | Description |
|---|---|---|
| Expression | Yes | A predicate expression using ? placeholders for values, for example headline contains ? and (cms.content.publishDate > ? or featured = ?). It supports and, or, not, parentheses, positional binding such as ?0 and ?1, and keywords like missing. |
| Values | No | Values substituted for the placeholders, in order. Each accepts variables. A note warns when the count doesn't match the placeholders in the expression. |
Work Stream
Runs across a saved, progress-tracked work stream in the connected CMS.
| Field | Required | Description |
|---|---|---|
| Work Stream | Yes | The work stream to run across. |
| Include Completed | No | By default only items not yet completed in the work stream are returned, so a re-run picks up where the last one left off. Turn it on to return every item regardless of completion. |
| Max Results | No | Caps how many items are returned and iterated. Defaults to 100; the CMS caps it at 1000. |
Pair a work stream source with the Content action's Complete Work Stream Item operation inside the loop, and each run works through what the last one left.
Output
results—a list of matched content, each a summary with its id, type, and label. totalCount and truncated report the full match count and whether Max Results cut the list short. With a Work Stream source, the output also identifies the work stream, so a later Complete Work Stream Item can reference it.