---
title: Query Filter Decision node
description: "Configure the Query Filter Decision node to check whether a user's profile attributes match a specified query filter, for use in progressive profile and conditional journey flows."
component: platform
version: 7.5
page_id: platform:auth-node-ref:query-filter-decision
canonical_url: https://docs.pingidentity.com/platform/7.5/auth-node-ref/query-filter-decision.html
llms_txt: https://docs.pingidentity.com/platform/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-query-filter-decision.adoc"]
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
  example: Example
---

# Query Filter Decision node

The Query Filter Decision node checks if the contents of a user's profile match the specified query filter.

Use this node to check whether an attribute of the user profile matches a specific pattern. For instance, use this in progressive profile flows to check if marketing preferences are set on a user's profile.

## Availability

| Product                                                                                                                                 | Available? |
| --------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud                                                                                                         | Yes        |
| PingAM (self-managed)

This functionality requires that you configure AM as part of a sample Ping Identity Platform deployment. | Yes        |
| Ping Identity Platform (self-managed)                                                                                                   | Yes        |

## Inputs

This node reads the Identity Attribute from the shared node state. If it can't read the Identity Attribute, it reads the `userName`.

It uses the value to look up the identity object.

## Dependencies

This node depends on IDM to look up the user object.

## Configuration

| Property           | Usage                                                                                                                                                                                                                                                                |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Query Filter       | A query filter used to check the contents of an object.Find details on constructing effective query filters in [Construct queries](https://docs.pingidentity.com/pingidm/7.5/objects-guide/queries.html#constructing-queries) in the IDM documentation.Default: none |
| Identity Attribute | The attribute used to identify the managed object in IDM.Default: `userName`                                                                                                                                                                                         |

## Outputs

None.

## Outcomes

* `True`

  The node user profile matched the query.

* `False`

  Any other case.

## Errors

This node doesn't log error or warning messages of its own.

## Example

Other journeys invoke the following progressive profile journey to capture missing profile attributes:

![Testing whether an account has profile attributes](_images/query-filter-decision-example.png)

* The [Login Count Decision node](login-count-decision.html) triggers the rest of the journey depending on the login count and its settings.

* The Query Filter Decision node determines whether managed object profile fields are missing.

* The [Attribute Collector node](attribute-collector.html) in the [Page node](page.html) requests additional input for the profile.

* The [Patch Object node](patch-object.html) stores the additional input in the managed object profile.