> For the complete documentation index, see [llms.txt](https://ledsak.gitbook.io/docs-for-ledsak/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ledsak.gitbook.io/docs-for-ledsak/automation.md).

# Automation

#### We enable you to create unlimited automated workflows tailored to your specific needs, whether you're managing multiple products, teams, or sales processes.

### 📘 **Automation Setup Guide**

This guide helps you understand how to create an automation that performs specific actions based on triggers and conditions for leads in your system.

#### Guide Tutorial:

{% embed url="<https://www.loom.com/share/8be1cd167cb441a8a57aaf3ea31ab574?sid=b0bcc81c-3653-4c50-8cc6-c757e16ab4f4>" %}

***

#### 🛠️ **Step-by-Step: Creating an Automation**

#### 1. **Automation Title**

* Enter a name for your automation.\
  Example: `Assign Lead Based on Source`

***

#### 2. **Trigger Configuration**

* **Trigger Type**: Choose what should start the automation.\
  Options include:
  * `New Lead Created`
  * `Lead Updated`
  * `Activity Logged`
* **Trigger Action**: Select a specific event related to the trigger.\
  Example: If Trigger Type is “Lead Updated”, Trigger Action could be “Status Changed”.

***

#### 3. **Setup Section (Optional)**

* Click on **`+ Add Setup`** to add a setup block.
* **Setup Type**: Choose any additional setup logic or prerequisites that must happen before the condition check.<br>

***

#### 4. **Conditions**

* Conditions define the rules that must be met to execute the actions.

You can add multiple conditions. Each condition has:

* **Type**: Choose from:
  * `Lead Fields` (e.g., name, email, city)
  * `Group`
  * `Stage`
  * `Branch`
  * `Source`&#x20;
  * `User`
* **Field Name**: Select the specific field relevant to the selected type.
* **Condition**: Set the logic (e.g., Equals, Contains, Starts With, etc.)
* **Value**: The actual value you want to compare against.

💡 Example:

* Type: `Source`
* Field Name: `Lead Source`
* Condition: `Equals`
* Value: `Website Form`

***

#### 5. **Actions**

* Choose what should happen when the condition is true.

Each action includes:

* **Action Type**:\
  Example: `Field Update`, `Send Email`, `Assign to User`, etc.
* **Field/Action Detail**:\
  Example: `Assign Lead Field to Sales Team`

➡️ You can add more than one action by clicking **`+ Add Action`**.

***

#### ✅ **Final Step: Save Automation**

Click **`Save Automation`** once everything is configured. Your automation will now run whenever the defined trigger and conditions are met.

***

### 🔄 Example Use Case

**Automation Title**: *Assign Website Leads to Sales*

* **Trigger Type**: Lead Trigger&#x20;
* **Trigger Action**: New Lead
* **Setup Type:** Any condition can be met
* **Conditions**:
  * Type: Source
  * Field Name: Lead Source
  * Condition: Equals
  * Value: Website Form
* **Actions**:
  * Action Type: Assigned To Team
  * Assign Lead Field: Assign to `Sales Team`&#x20;

***

#### Key Observations:

1. **Clarity**:
   * Automation is made more powerful and accessible—no coding expertise required.
2. **Improvements**:
   * Easy to Automate Bases on Lead Field, Stage, Group, Branch, Assigned user, Activity Workflow.
   * Actions types- User update, team update, source update, stage update, group update, Email for first lead come, Whatsapp for first lead come.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ledsak.gitbook.io/docs-for-ledsak/automation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.