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

# Update

#### 🎯 **What does this operation do?**

This operation allows you to update the data of a **card** already registered within a **workspace**, enabling the editing of information such as:\
✅ Card name\
✅ Description\
✅ List within the board\
✅ Responsible user\
✅ Associated tags\
✅ Estimated completion date\
✅ Custom fields

***

### 📂 **How to Configure the "Update" Operation**

#### 1️⃣ **Access the Component**

1. In **Hablla Studio**, open the automation flow where you want to update a card.
2. Add the **Cards**.
3. In **right side panel**, select the operation **"Update"**.

***

#### 2️⃣ **Fill in the Required Fields**

* **Workspace ID** → Identifier of the workspace where the card is located.
* **Card ID** → Identifier of the card to be updated.

***

#### 3️⃣ **Choose the Fields to Be Updated**

You can modify one or more of the following fields:

* **Card Name** → Update the card name.
* **Description** → Modify the card description.
* **Board** → Change the board where the card is located.
* **List** → Move the card to a new list within the board.
* **Assignee (User)** → Update the card owner.
* **Tags** → Add or remove tags associated with the card.
* **Expected Date** → Modify the task's estimated completion date.
* **Followers** → Add or remove users who should follow the card.
* **Custom Fields** → Update extra information configured in the workspace.

***

#### 4️⃣ **Save the Configuration**

After filling in the desired fields, click the button **"Save"** ✅.

Now, whenever this automation is triggered, the card data will be **updated automatically** in the system.

***

### 📌 **Usage Example in an Automation Flow**

📊 **Scenario**: Create a flow where the status of a **qualified lead** is updated within a card on the **opportunities board**.

1️⃣ **Block 1** → Capture a new lead via form.\
2️⃣ **Block 2** → Check if the card already exists on the board.\
3️⃣ **Block 3** → Update the card with new lead information, including tags and owner.

🚀 **Result**: The card is updated automatically whenever there are changes in the lead's status, ensuring the sales team works with always up-to-date information!

***

### 🎉 **Conclusion**

The operation **Update Card** in the **Hablla Studio** is essential to maintain the organization and accuracy of information in automated workflows.

If you need more support, contact our team! 🚀


---

# 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/cards/update.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.