> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/hablla/people/remove-organization.md).

# Remove Organization

The Remove Organization operation allows unlinking a person record from an organization (company) record. Keeping associations between contacts and companies up to date is crucial for the accuracy of your B2B data.

This action is normally used when a contact changes jobs or when a link was made incorrectly. By removing the association, you ensure that the person is no longer considered part of that organization in your segmentations, reports, and automations.

The operation only removes the link with the specified organization, not affecting other associations the person may have.

#### How to Configure

1. In Hablla Studio, add the "People" block to your automation flow.
2. In the "Operation" field, select the "Remove Organization" option.
3. In the "Person ID" field (`personId`), enter the identifier of the contact from which the organization will be dissociated.
4. In the "Organization" field, select the organization you wish to remove from the person's profile.

### Parameters

| Field        | Type                  | Required? | Description                                                                        |
| ------------ | --------------------- | --------- | ---------------------------------------------------------------------------------- |
| Person ID    | Text                  | ✅ Yes     | The unique ID of the person (contact) from whom the organization will be unlinked. |
| Organization | List of Organizations | ✅ Yes     | The organization to be dissociated from this person.                               |

### Structure (Using JSON)

The JSON request body must contain an array called `organizations` with the ID(s) of the organization(s) to be removed.

JSON

```
{
  "organizations": [
    "organization_id_abc123"
  ]
}
```

***

### 🚀 Example Use Case

Purpose: When a contact's email results in a "hard bounce" and the error message indicates that the person no longer works at the company, remove the association with the organization.

1. Create a flow triggered by a Webhook from your email service that fires on a "hard bounce" with a specific message (e.g., "User not found").
2. The trigger receives the contact's email. Use the "Find Person by Email" operation to obtain the `personId` and the person's data, including the organization they belong to (`person.organizations[0].id`).
3. Add the "People" block with the "Remove Organization" operation.
   * Person ID: Use the ID found in the search (`{{steps.2.result.id}}`).
   * Organization: Use the ID of the organization also found in the search (`{{steps.2.result.organizations[0].id}}`).
4. Optionally, add an "Ex-employee" tag to that person to record the reason for the change.

With this automation, you proactively clean your database, ensuring that your contact lists by company are always accurate and reliable.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/hablla/people/remove-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.