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

# Delete

The Delete Task operation (delete) allows you to remove a task from the system, ensuring that unnecessary or obsolete records are properly eliminated.

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

This operation permanently deletes a task within a workspace. Once deleted, the task cannot be recovered.

✅ Removes a specific task from the system.\
✅ Disassociates any relationship of the task with cards, people, or organizations.\
✅ Keeps the workspace organized and free of unnecessary tasks.

***

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

| **Field**        | **Data Type** | **Required?** | **Description**                               |
| ---------------- | ------------- | ------------- | --------------------------------------------- |
| **Task ID**      | `string`      | ✅ Yes         | Unique identifier of the task to be deleted.  |
| **Workspace ID** | `string`      | ✅ Yes         | ID of the workspace where the task is stored. |

***

### ✅ **Step by step to Set Up the "Delete" Operation**

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

1. In **Hablla Studio**, open the automation flow where you want to delete a task.
2. Add the block **Tasks**.
3. In **right side panel**, select the operation **"Delete"**.

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

🔹 **Task ID** → Enter the identifier of the task that will be removed.\
🔹 **Workspace ID** → Specify the workspace to which the task belongs.

#### 3️⃣ **Confirm Deletion**

📌 **Warning:** Task deletion is irreversible. Make sure the action is necessary before saving.

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

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

Now, whenever this automation is triggered, the corresponding task will be automatically removed from the system.

***

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

📊 **Scenario:** Automatically delete tasks when a process is completed.

1️⃣ **Block 1** → Check if an opportunity has been closed.\
2️⃣ **Block 2** → Fetch tasks associated with the process.\
3️⃣ **Block 3** → Automatically delete completed tasks.

🚀 **Result:** The system keeps only relevant tasks, ensuring efficient organization.

***

### 🎉 **Conclusion**

The operation **Delete Task (delete)** in the **Hablla Studio** helps keep an organized environment by removing tasks that are no longer needed. Use this feature with caution to avoid losing important information.

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/delete.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.