# Workflow Action – Remove Associated Records from Workflow

> Use Remove Associated Records from Workflow in GHL Customer Care to unenroll related contacts, companies, or custom objects by label

- Source: https://docs.ghlcustomercare.com/docs/workflows/crm-workflow-actions/workflow-action-remove-associated-records-from-workflow
- Section: Workflows / CRM Workflow Actions
- Reading time: 2 min
- Images: 1, each explained below

---
**TABLE OF CONTENTS**

-   [Overview](#overview)
-   [Action Name](#action-name)
-   [Action Description](#action-description)
-   [Action Details](#action-details)
-   [Examples](#examples)

## Overview

The Remove Associated Records from Workflow action is available in all workflow types — Contact-based, Company-based, and Custom Object-based workflows. It automatically **removes records that are associated to the trigger record** (via a selected object + label) from another workflow. This ensures clean unenrollment of related contacts, companies, or custom object records when conditions change.

This action is different from the existing [Remove from Workflow action](https://docs.ghlcustomercare.com/docs/workflows/internal-tools-workflow-actions/workflow-action-remove-from-workflow) which only removes the current record (e.g., a contact) from a workflow. Remove Associated Records from Workflow instead allows you to unenroll associated records (Contacts, Companies, or Custom Objects) based on an association label.

## Action Name

Remove Associated Records From Workflow

## Action Description

This action enables workflow users to:

-   Select an **object type**
    
-   Choose an **association label** to target which associated records should be removed.
    
-   Pick the **workflow** the associated records will be removed from.
    

This action is possible only after creating custom objects (or using contacts/companies) in the sub-account and ensuring that an **association label** exists between the trigger record and the records to be removed. This includes **contact-to-contact** and **company-to-contact** associations.

## Action Details

![Action Details (image 1 of 1)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155054812396/original/5fxj8Jwe5eWzFilNjCjFCjgaPgYdH7KDig.png)

**Action Details (image 1 of 1)**

This screenshot appears in the "Action Details" section of "Workflow Action – Remove Associated Records from Workflow". The text alongside this image reads: This action is possible only after creating custom objects (or using contacts/companies) in the sub-account and ensuring that an association label exists between the trigger record and the records to be removed. This includes contact-to-contact and company-to-contact associations. This part of the guide covers 1 field, listed below. Immediately after, the guide continues: Select an object: Choose the type of associated records to remove (e.g., Contacts, Dealers, Properties). Association Label (required): Determines which associated records qualify for removal. (does not apply on company - contact….
- What this covers: This action is possible only after creating custom objects (or using contacts/companies) in the sub-account and ensuring that an association label exists between the trigger record and the records to be removed. This includes contact-to-contact and company-to-contact associations.
- Fields: Edge cases & notes:
- Controls: Select an object, Association Label, Workflow, removed from, Edge cases & notes, Add Associated Records to Workflow
- Next: Select an object: Choose the type of associated records to remove (e.g., Contacts, Dealers, Properties). Association Label (required): Determines which associated records qualify for removal. (does not apply on company - contact associations) Workflow: Select the target workflow the associated records will be removed from. Edge cases & notes:

Full procedure:

1. Select an object: Choose the type of associated records to remove (e.g., Contacts, Dealers, Properties).
2. Association Label (required): Determines which associated records qualify for removal. (does not apply on company - contact associations)
3. Workflow: Select the target workflow the associated records will be removed from.
4. Edge cases & notes:

-   **Select an object**: Choose the type of associated records to remove (e.g., Contacts, Dealers, Properties).
    
-   **Association Label** (required): Determines which associated records qualify for removal. (does not apply on company - contact associations)
    
-   **Workflow**: Select the target workflow the associated records will be **removed from**.
    
-   **Edge cases & notes**:
    
    -   At least one matching association (by label) must exist; otherwise, no records are removed.
        
    -   Removals are immediate; if you need to re-enroll later, use **Add Associated Records to Workflow** action or a separate automation.
        

## Examples

#### **Example 1: Car ↔ Dealer (Custom Object Workflow)**

When a **Car** record’s status changes to _Sold_, remove its associated **Dealers** (label: _Assigned Dealer_) from the **Dealer Notification Workflow** so they stop receiving updates.

**Setup**

-   **Object** → Dealer
    
-   **Association Label** → Assigned Dealer
    
-   **Workflow** → Dealer Notification Workflow
    

**How It Works**

1.  Car status becomes _Sold_ (workflow trigger).
    
2.  Action finds Dealers associated to the Car via _Assigned Dealer_.
    
3.  Those Dealers are removed from the _Dealer Notification Workflow_.
    

---

#### **Example 2: Contact ↔ Contact (Parent–Child, Contact Workflow)**

When a **Student Contact** graduates, remove all **Parent Contacts** (label: _Parent-Child_) from the **Semester Start Notification** workflow.

**Setup**

-   **Object** → Contact (Parent)
    
-   **Association Label** → Parent-Child
    
-   **Workflow** → Semester Start Notification
    

**How It Works**

1.  Student record triggers the workflow on _Graduated_.
    
2.  Action finds Parents associated via _Parent-Child_.
    
3.  Those Parents are removed from the _Semester Start Notification_ workflow.
    

---

#### **Example 3: Company ↔ Contact (Company Workflow)**

When a **Company** record’s status changes to _Inactive_, remove all **Contacts** from the **Active Clients Communication Workflow**.

**Setup**

-   **Object** → Contact
    
-   **Workflow** → Active Clients Communication Workflow
    

**How It Works**

1.  Company record is updated to _Inactive_.
    
2.  Those Contacts are removed from the _Active Clients Communication Workflow_.
    

---

---

Documentation for GHL Customer Care. Support: support@ghlcustomercare.com