# Automation Component

### Trigger

Lead Automation will only work on leads that were modified after the trigger was created. Each trigger has specific rules, and when those rules are met one or more actions are performed.

| Icon                                                                 | Description                                                                                                                                                           |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ​​ <img src="/files/-MU7PXglpt0OvL8_H1dQ" alt="" data-size="line"> ​ | These fields will allow you to trigger based on the sales that handled the leads, like trigger by **'Sales'**, **‘Sales Manager'**, or **'Sales and Sales Manager'**. |
| ​​ <img src="/files/-MU7Pf1ss4DvYpBlYITM" alt="" data-size="line"> ​ | These fields will allow you to trigger based on the leads from the group.                                                                                             |
| ​​ <img src="/files/-MU7Pma_sMegrfIdqlvk" alt="" data-size="line"> ​ | These fields will allow you to trigger based on the lead, like archived, unarchived, and converted.                                                                   |

### Filter

The filter section has two areas to allow you to tightly define what leads meet the trigger criteria. In the top section you define conditions that ALL have to be met (a logical **Is**), and in the bottom section, you list conditions where any of the items can't be met (logical **Is not**). Any number of filters can be added.

| **Icon**                                                        | **Description**                                                             |
| --------------------------------------------------------------- | --------------------------------------------------------------------------- |
| <img src="/files/-MU7QX7rInV13avcVJDL" alt="" data-size="line"> | You can display action of lead automation based on label, source, or value. |
| <img src="/files/-MU7Ql1jSpQaap-J9wNg" alt="" data-size="line"> | All of condition block 1 **Is** from condition block 2.                     |
| <img src="/files/-MU7QwOF_esguZ6IJVFM" alt="" data-size="line"> | All of condition block 1 **Is not** from condition block 2.                 |

### Action

Once the trigger conditions have been defined, you can configure actions to be performed when the conditions have been met. Any number of actions can be added. Here is the list of available actions :

| **Icon**                                                            | **Description**                                                                        |
| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| <img src="/files/-MU7RJB_nLefb3HbDP6l" alt="" data-size="original"> | Associate the selected label with the leads.                                           |
| <img src="/files/-MU7RW7HhocYDMmUAQLG" alt="" data-size="original"> | This will set the owner of the leads (like which user that will be handled this leads) |
| <img src="/files/-MU7Ree-6CwpBdVgLLy5" alt="" data-size="original"> | This will set the status of the leads (like Archived or Active)                        |
| <img src="/files/-MU7S-VKquYtWpU11pK2" alt="" data-size="original"> | Associate the selected process flow keyword with the leads.                            |


---

# Agent Instructions: 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:

```
GET https://docs.3dolphins.ai/sales-activity/lead/lead-automation/automation-component.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.