The Wait action lets you control the timing of your automation by pausing the flow before moving to the next step. It's particularly useful when managing multiple actions that need to be spaced out based on time, task completion, or user behavior.

You can set it to create a simple time delay, wait for a task to finish, track engagement with an email, monitor changes to a record, or even use custom code for more advanced conditions. Designed for flexibility, the Wait action is easy to configure and offers options like skipping weekends, setting timeout branches, and naming each wait step for better clarity.

How to Set Up the Wait Action

Name: Give your Wait action a clear name so you can easily identify it later.

Exclude Weekends: Decide whether to count weekends in the waiting period by selecting Yes or No from the dropdown.

Wait Type: Choose from various wait types using toggle buttons. Each option can be configured to fit your specific needs.

Select Your Wait Type

For a Duration

Specify exactly how long the Wait action should pause by entering the desired duration using this format:

1h for one hour

2w for two weeks

3d for three days

…and so on.

Task Completion

Email opened or clicked

With this option, you can configure the Send Email action in the Step field, but it must be placed before the Wait action in the sequence.

You can specify how long the system should wait for the email to be opened or clicked, using the same method as the "For a Duration" mode.

Additionally, by selecting the Branch on Timeout checkbox, the system will send a reminder email if the original message isn’t opened within the defined timeframe.

Event

This tracks a set of conditions based on the fields within the record that triggers the automation. The fields available will vary depending on the record itself.

You can also define a timeout duration and enable the Branch on Timeout option. If the conditions aren’t met within the specified time, a reminder will be sent to the record owner to take action.

For example, if the condition is set to trigger when the Lead Stage is marked as Partner or MQL, the event occurs and the automation continues from there.

Custom Code

This mode allows you to define rules using your own code. The action will pause and wait until the specified conditions are met. Keep in mind that the custom code works based on a previous Step—an action placed before the Wait action in the automation flow.

You can choose from actions like Find Record, Update Record, Create Task, or use the Triggering Record, which is the record that initiated the automation. Your custom code should be written according to the data available from the selected step.

Custom Wait Durations for Specific Conditions

In Custom Code mode, you can go beyond setting a single wait time for all conditions. Instead, assign unique wait durations to each individual condition. This lets you fine-tune your automation, ensuring each scenario follows its own precise timing—making your process more efficient and targeted.

If you want to know more about other actions for the automation builder, check this article.