> 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/get-by-id.md).

# Get by ID

The Get by ID operation (get\_by\_id) allows you to retrieve the details of a specific task within the system, making it easier to obtain accurate information for tracking and process automation

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

This operation fetches a specific task by its unique identifier within a workspace.

✅ Returns the complete details of a registered task.\
✅ Allows viewing status, description, dates, and assigned users.\
✅ Can be used in automated workflows to retrieve information before performing an action.

***

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

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

***

### ✅ **Step-by-step to Configure the "Get by ID" Operation**

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

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

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

🔹 **Task ID** → Enter the identifier of the task you want to retrieve.\
🔹 **Workspace ID** → Specify the workspace to which the task belongs.

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

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

Now, whenever this automation is triggered, the task's detailed information will be retrieved automatically.

***

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

📊 **Scenario:** Obtain details of a task before performing an automatic update.

1️⃣ **Block 1** → Receive the task ID from an event or external integration.\
2️⃣ **Block 2** → Fetch the task's full details by ID.\
3️⃣ **Block 3** → Update the task with new information, if necessary.

🚀 **Result:** The automation obtains the necessary task details before any subsequent action.

***

### 🎉 **Conclusion**

The operation **Fetch Task by ID (get\_by\_id)** in the **Hablla Studio** is essential for retrieving accurate information about a task in any automation flow. This functionality allows validating data before updates and facilitates intelligent integrations.

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/get-by-id.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.