# Create

### 🎯 What does this operation do?

This operation creates a new task within a workspace, allowing the filling in of information such as: 

✅ Task name\
✅ Detailed description\
✅ Task type (call, meeting, email, etc.)\
✅ Responsible user\
✅ Start and end date\
✅ Association with people, cards, organizations and services\
✅ Task checklist

### 📂 How to Configure the "Create" Operation

1️⃣ **Access the Component**\
In **Hablla Studio**, open the automation flow where you want to create a task.

2️⃣ **Add the "Tasks" Block**\
In the right side panel, select the operation **Create**.

3️⃣ **Choose How to Specify the Body**\
You can specify the task data U**sing Fields** or **Using JSON**.

### 🔹 **Specify Body: Using Fields**

If the option **Using Fields** is selected, the following fields can be filled in:

| Field                    | Type            | Required | Description                                                                                                                                   |
| ------------------------ | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Task Name**            | `string`        | ✅ Yes    | Name or title of the task being created.                                                                                                      |
| **About**                | `string`        | ✅ Yes    | Detailed information about the task.                                                                                                          |
| **Description**          | `string`        | ✅ Yes    | Detailed description of the task.                                                                                                             |
| **Task Type**            | `string (enum)` | ✅ Yes    | Specifies the type of task, such as call, meeting, email, etc.                                                                                |
| **Start Date**           | `datetime`      | ✅ Yes    | Start date and time of the task.                                                                                                              |
| **Finish Date**          | `datetime`      | ✅ Yes    | Expected date and time for task completion.                                                                                                   |
| **Responsible User**     | `string`        | ❌ No     | ID of the user responsible for carrying out the task.                                                                                         |
| **Associated Person ID** | `string`        | ❌ No     | ID of the person related to the task.                                                                                                         |
| **Organization ID**      | `string`        | ❌ No     | ID of the organization related to the task.                                                                                                   |
| **Associated Card ID**   | `string`        | ❌ No     | ID of the card to which the task is linked.                                                                                                   |
| **Sector**               | `string`        | ❌ No     | Sector or department related to the task.                                                                                                     |
| **Checklist**            | `array`         | ❌ No     | List of items to be checked or completed within the task. Each item in the array must follow the structure: `{ "item": "Item description" }`. |

✅ After filling in the fields, click **Save** to complete the configuration.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FaDIKVesTS6E7xIDO3nXd%2Fimage.png?alt=media&#x26;token=252b40db-a13b-4481-b053-1c9bd9b0cc93" alt=""><figcaption><p>Call task for in 20 minutes lasting 20 minutes</p></figcaption></figure>

### 🔹 **Specify Body: Using JSON**

If the option **Using JSON** is selected, use the following format to send the task data:

```json
{
  "name": "Meeting with client",
  "description": "Discuss commercial proposal and align next steps.",
  "about": "This task is part of the sales pipeline.",
  "type": "meet",
  "color": "blue",
  "user": "idUser",
  "start_date": "2025-03-04T10:00:00Z",
  "finish_date": "2025-03-04T11:00:00Z",
  "person": "idPerson",
  "card": "idCard",
  "service": "idService",
  "organization": "idOrganization",
  "sector": "idSector",
  "checklist": [
    {
      "name": "Prepare presentation",
      "done": false,
      "order": 1
    },
    {
      "name": "Confirm client's availability",
      "done": true,
      "order": 2
    }
  ]
}
```

#### 🔍 **ID Format**

The fields `person`, `card`, `service`, `organization`, `sector` and `user` must contain IDs in the following format:

```
674f6ee3debc8828cde11e3b
```

To make reading easier, the placeholders were used in the example above `idPerson`, `idCard`, `idService`, `idOrganization`, `idSector` and `idUser`.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FECmgvOVqdfBdcZGxBZuP%2Fimage.png?alt=media&#x26;token=b739828b-d01a-4efc-933f-32410c3afde1" alt=""><figcaption></figcaption></figure>

✅ After inserting the JSON correctly, click **Save** to complete the configuration.

***

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

#### 🎯 Scenario: Automatically create a task for a new sales opportunity.

1️⃣ **Block 1** → Capture a new lead via form.\
2️⃣ **Block 2** → Create a new task in the CRM for follow-up.\
3️⃣ **Block 3** → Set the user responsible for the task.

🚀 **Result:** Whenever a new lead is captured, a task will be automatically created for follow-up.

### 🎉 **Conclusion**

The operation **Create Task** in Hablla Studio allows you to organize and automate the management of activities within the system. You can choose between configuring the fields manually or using a **JSON** custom for greater flexibility.

If you need more support, contact our team! 🚀