Contents:

• Overview
• Use Cases
• Prerequisites
• Account Hierarchy Match Node Overview
• Configure the Account Hierarchy Match Node
• Best Practices
• Troubleshooting & FAQs
• Summary

 

Overview

The Account Hierarchy Match node lets you retrieve one or more related Accounts from a selected Account’s full LeanData Account Hierarchy and store the results in a variable for use later in your FlowBuilder graph.

If you need help building the hierarchy data or setting up the Salesforce visualization first see Account Hierarchies - Setup and Visualization Guide.

 

Use Cases

Use the Account Hierarchy Match node when you need hierarchy-aware logic in your FlowBuilder graph, such as:

• Routing a record based on a field that only exists on the top-level parent Account.
• Updating a set of Accounts (for example, all children or descendants) when a value changes at the parent level.
• Finding a specific “regional” parent or subsidiary within an enterprise hierarchy using filters.

Example scenarios include:

• Route a new Contact to the ultimate parent Account owner.
• When a parent Account owner changes, update owners across all descendants.
• Find and route to the most relevant subsidiary (for example, “Sony USA”) instead of routing to the global parent.

 

Prerequisites

Before you configure this node, confirm the following:

• Account Hierarchies is enabled in your LeanData instance.
• You have already built an Account Hierarchy in LeanData.
• You have access to edit the relevant FlowBuilder graph.

If you have not built the hierarchy yet, complete the mapping and build steps first (covered in Account Hierarchies - Setup and Visualization Guide).

 

Account Hierarchy Match Node

At a high level, the Account Hierarchy Match node:

1. Takes an input Account (from a variable) and the specific LeanData hierarchy you want to evaluate against.
2. Uses the selected hierarchy build to locate that Account's hierarchy members.
3. Applies your selected member scope (for example, parent only, children only, or entire hierarchy).
4. Optionally filters the members.
5. Returns either a single Account or a collection of Accounts, stored in an output variable.

Configure the Account Hierarchy Match Node

1) Add the node to your graph

1. Open the FlowBuilder graph you want to update.
2. In the node bar, in the Match Nodes section, find and drag the Account Hierarchy Match node into your graph.
3. Connect it to the appropriate upstream node.

2) Select the Account to reference

1. In the node configuration panel, under Account Selection, select the variable that contains the Account you want to use as the starting point.
2. Common examples include:
   • A “Matched Account” variable returned from a prior match node.
   • A routed record’s related Account field (depending on the router type and your setup).

3) Select the hierarchy to evaluate

1. In the node configuration panel, under Hierarchy Selection, choose which LeanData Account Hierarchy this node should traverse. Each Account Hierarchy Match node evaluates the hierarchy you select here, so different match nodes in the same graph can target different hierarchies if your org maintains more than one.

4) Select the hierarchy members you want to return

• Under Hierarchy Member Selection, choose the hierarchy member(s) you want to return, such as:
  • Top-Level Parent
  • Direct Parent
  • Direct Children
  • All Descendants
  • Entire Hierarchy

5) (Optional) Add filters

• If you selected an option that returns multiple hierarchy members (Direct Children, All Descendents, or Entire Hierarchy) you can optionally configure filters to include or exclude hierarchy members based on Account field values.
• If you are not sure whether filters are needed, start without filters and add them once you confirm the node returns the expected members.

6) Choose an output type and output variable

• You will only see the following options if you selected an option that returns multiple hierarchy members (Direct Chidren, All Descendents, or Entire Hierarchy) in the Hierarchy Member Selection section above.
• Decide whether you need:
  • One Account (single record), or
  • Multiple Accounts (collection)
• If selecting One Account, you will have to configure prioritization rules (tiebreakers) to select the account

• If selecting Multiple Accounts, you will have to decide how the Accounts in the collection will be sorted, and the maximum number accounts to store.

• Set the output variable where the result should be stored,

Once your Account or Collection of Accounts has been identified, you can reference this variable in downstream nodes.

Differences from “Match to Parent Account” (Lead-to-Account Match Node)

The “Match to Parent Account” option in the Lead-to-Account node only evaluates Salesforce’s standard Parent Account relationship.

The Account Hierarchy Match node:

• Evaluates a specifically selected LeanData hierarchy on each node, rather than a single global hierarchy build. Different match nodes in the same graph can target different hierarchies.
• Represents multi-level hierarchies even when Salesforce Parent Account is not populated.
• Lets you retrieve broader member scopes (for example, all descendants or the entire hierarchy).
• Supports optional filters.
• Can return either a single record or a collection.

 

Best Practices

• Build the hierarchy first. If the hierarchy build is incomplete or has issues, this node may not return the expected members.
• Be specific with member scope. Returning the “Entire Hierarchy” can create extra downstream work if you only need one parent.
• Use filters to narrow results. Filters can help you target the right subsidiaries or exclude irrelevant branches.
• Prefer single-record outputs for assignment. If you only need one Account to drive routing, returning one record is usually simpler.
• Review the audit log when troubleshooting. Audit logs capture which hierarchy each Account Hierarchy Match node evaluated, making it easier to trace routing decisions when multiple hierarchies are in use.

 

Troubleshooting & FAQs

Why is the node returning no results?

• Confirm the input variable contains an Account that exists in the specific hierarchy selected on the node, not just in any LeanData hierarchy build.
• Confirm the hierarchy build has completed successfully.
• If you are filtering, test again without filters to confirm whether filters are excluding all members.

Why is a yellow warning banner showing on the node?

• The hierarchy selected on the node is currently being rebuilt. The node will not function during the rebuild. Once the rebuild completes, normal operation resumes automatically.

Why am I getting unexpected Accounts back?

• Verify the selected member scope (for example, “Direct Children” vs “All Descendants”).
• Review filter conditions for unintended matches.

 

Summary

The Account Hierarchy Match node enables hierarchy-aware routing, updates, and notifications by retrieving one or more Accounts from a selected Account’s full LeanData hierarchy and storing the results in a variable.

For questions or additional assistance, please contact LeanData Support.