---
title: "Distro CRM Matching Nodes"
source_url: https://help.chilipiper.com/hc/en-us/articles/40817938970003-Distro-CRM-Matching-Nodes
article_id: 40817938970003
updated_at: 2026-04-22T15:24:15Z
---

## Who can use this feature?

Available on All Products or Routing & Scheduling

Available to Admins or Workspace Managers

[Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub)

CRM Matching Nodes are in Distro’s Flow Builder and are designed to make matching behavior more visible, understandable, and configurable within the routing path. Rather than hiding the matching logic inside routing rules, these nodes allow you to explicitly define matching behavior (e.g. lead-to-account, lead-to-opportunity) and route accordingly. 

* * *

#### Table of Contents

  * Using the CRM Matching Node
  * Matching Results in Distro Logs
  * Examples Use Cases



* * *

## Using the CRM Matching Node

CRM Matching Nodes can be added anywhere in the Flow Builder path after the entry and duplicate rules. Here’s how to set them up:

  1. **Add a CRM matching node** to the desired location on your router.
  2. Choose the relevant matching types such as:
     * Lead to Account
     * Lead to Opportunity
     * Lead to Case
     * Related Lead
     * Custom Object Matches
  3. Use **True/False** logic for each match type. Multiple matches can be combined using "AND" conditions.
  4. Combine the node with assignment rules (e.g. assign to Account Owner or SDR Owner) for better clarity and control.



![](https://help.chilipiper.com/hc/article_attachments/40820114065939)

* * *

## Matching Results in Distro Logs

CRM Matching Nodes provide clearer Distro logs, which helps with debugging and auditing:

  * The log clearly displays each match result (e.g., "CRM Matching: Lead to Account Match = True").
  * A direct link to the matched object (e.g. Account, Opportunity) is included.
  * Ownership assignments based on match results are traceable.



![](https://help.chilipiper.com/hc/article_attachments/40820114068115)

* * *

## Example Use Cases

**Lead to Account → Account Owner**

  * Match lead to account = True
  * Route to Account Owner if they belong to a specified team



**Lead to Account + Opportunity**

  * Lead to Account = True AND Lead to Opportunity = True → Route to AE Owner
  * Lead to Account = True AND Lead to Opportunity = False → Route to SDR Owner



**Assign via Variables**

Distro Variables can also be used in **Assign and Update Ownership** nodes to dynamically set ownership based on the matched record’s owner following a CRM Matching Node—more details on Variables [here](https://help.chilipiper.com/hc/en-us/articles/40800666122003-Distro-Variables).

  * Lead to Account = True
  * Lead to Opportunity = True
  * Use a variable to copy the Opportunity Owner to the Lead (no team required)
  * Reduces complexity and allows fast ownership assignment