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

# Get all

The Get All Cards operation (get\_all) allows you to retrieve a complete list of cards registered within a workspace. This functionality is useful for filtering, organizing, and processing multiple

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

This operation returns a collection of cards according to custom filters.

✅ Retrieves all cards from the workspace.\
✅ Allows applying filters such as status, tags, responsible user and more.\
✅ Useful for monitoring and generating reports.

***

### 📂 **How to Configure the "Fetch All" Operation**

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

1. In **Hablla Studio**, open the automation flow where you want to retrieve the cards.
2. Add the **Cards**.
3. In **right side panel**, select the operation **"Fetch All"**.

***

#### 2️⃣ **Filter Configuration**

To refine the search, you can apply optional filters, including:

* **Workspace ID** → Identifier of the workspace where the cards are located (Required).
* **Status** → Filter by card status (example: "In progress", "Completed", "Lost").
* **Tags** → Search for cards with specific tags.
* **Responsible user** → Filter by who is assigned to the card.
* **Creation date** → Retrieve cards created within a specific period.
* **List** → Filter for cards within a particular list.
* **Sorting** → Set whether results will be ordered by creation or update date.
* **Result limit** → Set how many cards will be returned per request (default: 50).

📌 **Important**: If no filter is applied, the operation returns all available cards.

***

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

After setting the desired filters, click the button **"Save"** ✅.

Now, whenever this automation is triggered, the system will return the list of filtered cards.

***

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

📊 **Scenario**: Create a flow where all cards with status "In progress" are processed automatically.

1️⃣ **Block 1** → Trigger the operation **Get All Cards** with filter "Status = In progress".\
2️⃣ **Block 2** → For each returned card, check the creation date.\
3️⃣ **Block 3** → If the card has not been updated for more than 7 days, send an alert to the responsible person.

🚀 **Result**: The system monitors the cards in progress and automatically notifies the sales team when necessary.

***

### 🎉 **Conclusion**

The operation **Get All Cards** in the **Hablla Studio** is essential for automations based on multiple records, allowing more efficient control of cards within the 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/cards/get-all.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.