> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/crm/crm-automations/crm-automations-in-crm-with-the-condition-does-the-lead-have-a-scheduled-meeting.md).
# CRM - Automations in CRM with the condition "Does the lead have a scheduled meeting?"
The condition "The lead has scheduled a meeting" is essential for identifying high-quality leads and improving the sales team’s efficiency.
Go to the **CRM**, and click on **Automations**;
Define the **title** and the **condition**, which, in this case, will be '*Does the lead have a scheduled meeting?*'.
Define the **settings**;
Configure the **condition** that must be met for the **automation to be triggered**.
Determine what you want the CRM to do when the condition is met.
In the example, we will use '**Send a notification to an employee**'. This will cause the employee to be alerted whenever the lead schedules a meeting.
*But you can define other conditions, such as:*
'**Create Task**': When a lead schedules a meeting, the CRM will automatically create a task related to that meeting and assign it to the sales representative responsible for handling that lead.
Define **who** the notification will be sent, and the **message** that will appear in the notification and click on **Save**;
After saving your automation, click on the '**Play**' icon to activate it.
**See similar articles:**
{% content-ref url="/pages/4a1c7e56fdf5b057a091070b52862d8b0cbe813f" %}
[CRM](/en/topics/general/crm.md)
{% endcontent-ref %}
---
# 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://docs.sprinthub.com/en/topics/general/crm/crm-automations/crm-automations-in-crm-with-the-condition-does-the-lead-have-a-scheduled-meeting.md?ask=&goal=
```
`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.
