> 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/block.md).

# Block

The Block Person operation allows you to change a contact's block status. A blocked person typically stops receiving communications and may be removed from certain automations, helping keep your contact base clean and respecting privacy requests.

This action can be used to either block or unblock a person, simply by changing the parameter value.

#### How to Configure

1. In Hablla Studio, add the "People" block to your automation flow.
2. In the "Operation" field, select the "Block" option.
3. In the "Person ID" field (`personId`), enter the unique identifier of the person whose block status you want to change.
4. Set the "Block" field to `true` to block or `false` to unblock.

***

### Parameters (Using Fields)

| Field              | Type             | Required? | Description                                                                                                  |
| ------------------ | ---------------- | --------- | ------------------------------------------------------------------------------------------------------------ |
| Person ID          | Text             | ✅ Yes     | The unique ID of the person to be blocked or unblocked.                                                      |
| Block (`is_block`) | Boolean (Yes/No) | ✅ Yes     | Defines the action to be taken. Select `true` (yes) to block the person or `false` (no) to remove the block. |

Export to Spreadsheets

***

### Structure (Using JSON)

The JSON request body is simple, containing only the key `is_block`.

To block a person:

JSON

```
{
  "is_block": true
}
```

To unblock a person:

JSON

```
{
  "is_block": false
}
```

***

### 🚀 Example Use Case

Goal: Automatically block a contact in Hablla when an email sent to them results in a "hard bounce" (permanent delivery failure).

1. Create a flow that uses a trigger from your email service (via Webhook) that fires when a "hard bounce" occurs.
2. The trigger will receive the recipient's email that failed.
3. Use the "Find Person by Email" operation to find the ID of the person corresponding to that email in Hablla.
4. Add the "People" block with the "Block" operation.
5. In the "Person ID" field, enter the ID variable found in the previous step (`{{steps.2.result.id}}`).
6. In the "Block" field, set the value to `true`.

With this automation, your contact base stays clean, avoiding future sends to invalid email addresses and improving your sending domain's reputation.


---

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