---
title: Query Filter Decision node
description: The Query Filter Decision node checks if the contents of a user's profile match the specified query filter.
component: auth-node-ref
version: latest
page_id: auth-node-ref::query-filter-decision
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/query-filter-decision.html
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-query-filter-decision.adoc"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/query-filter-decision.html
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
---

# 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.

## 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.

## Availability

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

1 This functionality requires that you configure AM as part of a [Ping Identity Platform deployment](https://docs.pingidentity.com/platform/8.1/sample-setup/).

## 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 the underlying identity service (PingIDM) to look up the user object.

## Configuration

| Property           | Usage                                                                                                                                                                                                     |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Query Filter       | A query filter used to check the contents of an object.Find more information in [Construct queries](https://docs.pingidentity.com/pingoneaic/idm-objects/queries.html#constructing-queries).Default: none |
| Identity Attribute | The attribute used to identify the managed object in the underlying identity service (PingIDM).Default: `userName`                                                                                        |

## Outputs

This node doesn't change the shared state.

## Outcomes

* `True`

  The node user profile matched the query.

* `False`

  Any other case.

## Errors

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