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

# Add Phone

The Add Phones operation allows you to insert one or more phone numbers into an already existing person record.

This action is especially useful to enrich a contact's profile over time. If a lead who initially provided only an email later provides their phone in an interaction, you can use this operation to complement the record without overwriting other data.

The operation adds the new phones to the person's contact list, keeping the ones that already existed.

#### How to Configure

1. In Hablla Studio, add the "People" block to your automation flow.
2. In the "Operation" field, select the "Add Phones" option.
3. In the "Person ID" field (`personId`), enter the unique identifier of the person to whom you want to add the phones.
4. In the "Phones" section, fill in the details of the phone number(s) you want to add.

***

### Parameters (Using Fields)

| Field     | Type              | Required? | Description                                                                                                                                                            |
| --------- | ----------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Person ID | Text              | ✅ Yes     | The unique ID of the person who will receive the new phone numbers.                                                                                                    |
| Phones    | Fields Collection | ✅ Yes     | A list containing one or more phones to be added. Each item in the list must include: `Type` (Personal or Business), `Phone` (the number) and `Is WhatsApp?` (yes/no). |

Export to Spreadsheets

***

### Structure (Using JSON)

The JSON request body must be an array called `phones`, containing one or more phone objects.

JSON

```
{
  "phones": [
    {
      "type": "business",
      "phone": "+5511987654321",
      "is_whatsapp": true
    },
    {
      "type": "personal",
      "phone": "+5511912345678",
      "is_whatsapp": false
    }
  ]
}
```

***

### 🚀 Example Use Case

Goal: When a customer responds to a satisfaction survey and provides their WhatsApp number for contact, add that number to their record in Hablla.

1. Create a flow that starts with a Webhook trigger, receiving the completed survey data (including the email and the new phone).
2. Use the "Find Person by Email" operation to find the `personId` of the customer based on the received email.
3. Add the "People" block with the "Add Phones" operation.
4. In the "Person ID" field, enter the ID variable found in the previous step (`{{steps.2.result.id}}`).
5. In the "Phones" section, map the phone data received in the trigger:
   * Type: Set to `personal`.
   * Phone: Map the phone variable coming from the webhook.
   * Is WhatsApp?: Set to `true`.

This way, your customers' profiles are automatically enriched with new contact information, centralizing communication and ensuring that the data is always up to date.


---

# 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/add-phone.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.