> 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/tasks/remove-item-from-the-checklist.md).

# Remove item from the checklist

The Remove Checklist Item operation allows you to delete a specific item within a task's checklist, ensuring cleanliness and organization of tasks in the system.

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

This operation permanently removes an item from a task's checklist, ensuring it no longer appears in the user interface or automation flows.

✅ Delete a specific checklist item from a task.\
✅ Keep things organized by removing obsolete or unnecessary items.

***

### 📂 **Fields and Data Types**

| **Field**        | **Data Type** | **Required?** | **Description**                                        |
| ---------------- | ------------- | ------------- | ------------------------------------------------------ |
| **Workspace ID** | `string`      | ✅ Yes         | ID of the workspace where the task is located.         |
| **Task ID**      | `string`      | ✅ Yes         | Identifier of the task to which the checklist belongs. |
| **Item ID**      | `string`      | ✅ Yes         | Identifier of the checklist item to be removed.        |

***

### ✅ **Step-by-step to Configure the "Remove Checklist Item" Operation**

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

1. In **Hablla Studio**, open the automation flow where you want to remove a checklist item.
2. Add the block **Tasks**.
3. In **right side panel**, select the operation **"Remove Checklist Item"**.

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

🔹 **Workspace ID** → Set the workspace where the task is located.\
🔹 **Task ID** → Provide the identifier of the task from which the item will be removed.\
🔹 **Item ID** → Enter the identifier of the checklist item that will be deleted.

#### 3️⃣ **Save the Configuration**

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

Now, whenever this automation is triggered, the checklist item will be removed permanently.

***

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

📊 **Scenario:** Automatically remove checklist items after a task is completed.

1️⃣ **Block 1** → Verify that the task has been completed.\
2️⃣ **Block 2** → Remove all associated checklist items.\
3️⃣ **Block 3** → Send a notification to the person responsible informing them that the checklist has been cleared.

🚀 **Result:** Whenever a task is completed, checklist items that are no longer needed will be removed automatically, keeping the workflow clean and organized.

***

### 🎉 **Conclusion**

The operation **Remove Checklist Item (delete\_checklist\_item)** in the **Hablla Studio** allows deleting unnecessary items and keeping checklists organized, ensuring a more efficient workflow.

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/hablla/tasks/remove-item-from-the-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.