# Get by ID

The Get Person by ID operation retrieves all information of a specific person record using its unique identifier (`personId`).

This action is one of the most used in automations because it allows loading the data of a known contact to use in subsequent steps, such as personalizing a message, making decisions based on their data (e.g., customer status), or simply verifying their information.

The result of this operation is a complete object containing all the person's fields, including custom fields.

#### How to Configure

1. In Hablla Studio, add the "People" block to your automation flow.
2. In the "Operation" field, select the "Get by ID" option.
3. In the "Person ID" field (`personId`), enter the unique identifier of the person you want to query. This value is usually obtained from a trigger or a previous step in the flow.

***

### Parameters

| Field                | Type             | Required? | Description                                                                                                                             |
| -------------------- | ---------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Person ID            | Text             | ✅ Yes     | The unique ID of the person to be queried.                                                                                              |
| Populate Person Data | Boolean (Yes/No) | ❌ No      | If set to `true`, the search may return additional related data, such as detailed organization information or other associated records. |

Export to Spreadsheets

***

### Output Structure (Example Result)

After execution, the result of this block will be a JSON object with the structure below, which can be accessed in subsequent steps (e.g., `{{steps.1.result}}`):

JSON

```
{
  "id": "person_abcdef123456",
  "name": "Juliana Souza",
  "about": "Marketing Manager at Example Company.",
  "photo_url": "https://example.com/juliana.jpg",
  "privacy": "granted",
  "customer_status": "customer",
  "is_blocked": false,
  "created_at": "2023-10-26T10:00:00Z",
  "updated_at": "2024-08-16T15:30:00Z",
  "users": [
    {
      "id": "user_xyz789",
      "name": "Carlos Andrade"
    }
  ],
  "phones": [
    {
      "type": "business",
      "phone": "+5511977775555",
      "is_whatsapp": true
    }
  ],
  "emails": [
    {
      "email": "juliana.souza@example.com"
    }
  ],
  "custom_fields": {
    "last_meeting_date": "2024-08-10",
    "satisfaction_level": "Very Satisfied"
  }
}
```

***

### 🚀 Example Use Case

Objective: Send a personalized welcome email to a new customer as soon as a deal is marked "Won."

1. Create a flow with the "Card Moved" trigger, configured for the "Won" stage of your sales funnel. The trigger will provide the `cardId` and the `personId` associated.
2. Add the "People" block with the "Get by ID" operation.
3. In the "Person ID" field, enter the corresponding trigger variable (e.g., `{{trigger.person.id}}`).
4. Add an email sending block in the next step.
5. In the email body, personalize the greeting using the data obtained in the previous step. For example: "Hello, `{{steps.2.result.name}}`! Welcome to our company."

This way, you use the person's real-time data to create much more personal and effective communication, fully automated.


---

# Agent Instructions: 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:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/hablla/people/get-by-id.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.