> 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-automation-function-delay-the-automation-start.md).

# CRM - Automation - Function: Delay the automation start

With SprintHub, you optimize your CRM automations by controlling the start time of each automation.\
You can define time limits for startup, allowing, for example, an automation to run only after another is completed, or after information in the Lead has been filled in or updated.

This way, you ensure that automations occur at the ideal moment, respecting dependencies between processes and ensuring the integrity and currency of the data before the next steps are executed.

{% hint style="danger" %}
 If this option is enabled, the automation will only start after the configured time (including trigger and condition checks).\
**NOTE:** This option is not applied when you start this automation in bulk (when publishing the automation).
{% endhint %}

{% hint style="info" %}
This limiter is also in 360º SAC Automations
{% endhint %}

1. Create an Automation:

* Access your CRM: Through “Find Services.” Or just type the name, and the function appears.
* Go to the Automations section.
* Start creating: Click on "Create Automation" using the "+" button.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf6j7KFb54AhT2DebLR9zIrS0QYwjDCx4TwQ3sK87QQ6tPuwjcDyynVOWGwfkasz6WhGwo2KWY07cDVhncZa36bsCpLhlBv3rlf7nnWele9vXtJdNvMrQBS0YGODplPXwkLFjTsFw?key=tzs9a5fx7MSTof5_7bHzCw" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe4eucdcpJTZlQSxz9oQn1kGKq7bIU7jrTNP35WsSgJ_HlqiP6ehAn2BTpMPQCIBlmmMJ1e5AwTah_lmKnTF31FTe_7YViKUCIgs9Rxw6nhSkkYw0uze2TzLrG5cw1CX46R3CXB?key=tzs9a5fx7MSTof5_7bHzCw" alt=""><figcaption></figcaption></figure>

2. **Configure and Save:**

* **Enter a Title:** Give the automation a descriptive name.
* **Configure a Trigger:** You can use a trigger of your choice.
* **Set up the Condition:** You can use one or more conditions of your choice.

> But attention: without using triggers, it will be necessary to enable condition checks. These checks will occur at varying time intervals, which can range from minutes to hours, depending on the number of automations and leads in your instance.

* **Choose the Action:** You can use one or more actions of your choice.
* **Configure the Action**.
* **Describe** exactly what the action will do.
* **Save the Automation:** After configuring, save the automation.

{% embed url="<https://youtu.be/FsoS8ifUbGQ>" %}

{% hint style="info" %}
To create this automation in the funnel, switch to the “Pipeline Automations” tab and click “+ New Automation.”
{% endhint %}

**CONCLUSION**

Controlling the startup time of automations in SprintHub helps make your workflows smarter and more organized, ensuring that each step happens at the right time and with the correct information. In addition to optimizing the Lead experience, this practice contributes to more efficient management of your sales and relationship processes.


---

# 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-automation-function-delay-the-automation-start.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.