Knowledge Base

Knowledge Base/Features/Automations/Automations: wait for...

Automations: wait for an event

YS
Yssel Salas
Last updated: October 19, 2026
Note: Automations is only available on Growth and higher plans.

The wait for an event step pauses an automation until a specific event happens. If the event doesn’t happen within a set time limit, the automation stops.

Use this step to control exactly when actions happen, for example:

  • Send a follow-up email only if a customer replies within three days
  • Create a follow-up activity for the sales team after the onboarding team completes an activity

Configure the wait for an event step

Note: You can add up to 10 wait for an event steps per automation. Learn more about automation limits in Pipedrive.

Create an automation as usual by setting a trigger and add at least one action step. The wait for an event step needs an earlier action to wait on, such as a sent email or a created activity.

Then select “Wait” and choose “Wait for an event”.

Define the event

After adding the step, define what the automation should wait for and for how long.

The event must be based on an item used earlier in the automation, such as an email, activity, deal, lead, organization, person, project or task.

You can then set specific conditions, like an email receiving a reply.

Set the time limit

Note: The maximum time limit for the wait for an event step is seven days.

Choose how long the automation should wait. You can select a predefined option or enter a custom duration.

Skip weekends in the time limit

When you choose the option to skip weekends, the weekend days still count towards the seven day limit. For example, if you set a two-day time limit on Friday, the time limit ends on Sunday. The wait step then ends on Monday, not Tuesday.

Once ready, click “Apply conditions” and continue building the rest of your automation.


Monitor wait for an event executions

You can track your automation’s performance in the automation overview tab.

Click on a status in the health chart to go to the automation history with the right filter already applied: done, failed, pending or stopped.

From there, click on an automation to see its execution in detail.

Understand execution statuses

  • Pending – the automation is waiting for the condition to be met or the time limit to expire
  • Done – the condition was met and the step completed successfully
  • Stopped – the time limit ended or a pending automation was stopped before the event happened. The automation doesn’t continue and the steps after the wait step aren’t performed.

Stop pending executions

If you want to stop a specific execution while it’s pending, click “Stop execution” next to the automation and confirm your choice.

Once you confirm, you can find this execution under the stopped filter.

If you need to deactivate the entire automation, you’ll be asked whether to keep current pending executions or cancel them all.

Was this article helpful?

Yes

No

Related articles

Got any questions?

Contact us