CaptainBook.io

The Delay action pauses workflow execution for a specified duration. The workflow automatically resumes after the delay period.

Workflow execution pauses at the delay step

Execution resumes automatically after the specified duration

Workflow context is preserved during the delay

- Workflow execution pauses at the delay step
- Execution resumes automatically after the specified duration
- Workflow context is preserved during the delay

___________________________________________________________

Time to wait before resuming. Supports multiple formats:

Format: <code>{number}{unit}</code> or <code>{number}{unit} {number}{unit}</code>

- <code>s</code> - Seconds
- <code>m</code> - Minutes
- <code>h</code> - Hours
- <code>d</code> - Days

<code>2h 30m</code> - 2 hours and 30 minutes

- <code>30m</code> - 30 minutes
- <code>2h</code> - 2 hours
- <code>1d</code> - 1 day
- <code>2h 30m</code> - 2 hours and 30 minutes
- <code>5m</code> - 5 minutes

Delay notifications (e.g., "remind me in 24 hours")

- Wait before sending follow-up emails
- Delay notifications (e.g., "remind me in 24 hours")
- Space out communication sequences
- Wait for external processes to complete
- Create time-based workflows

Send Notification (Ask for a review email)

1. Send Notification (Ask for a review email)
2. Delay (24h)
3. Send Notification (follow-up email)

1. Booking Confirmed trigger
2. Send Notification (confirmation)
3. Delay (1 day)
4. Send Notification (preparation tips)
5. Delay (1 day)
6. Send Notification (final reminder)

1. Booking Cancelled trigger
2. Delay (48h)
3. Send Notification (rebooking offer)

Delays pause the entire workflow execution

Maximum delay duration may be limited by your plan

- Delays pause the entire workflow execution
- The workflow will resume automatically
- Maximum delay duration may be limited by your plan
- Delays within loops are not supported

Use appropriate durations - Don't delay too long unnecessarily

Consider timezones - Be aware of recipient timezones

Test delays - Verify delay behavior in test mode

Monitor executions - Check that workflows resume correctly

1. Use appropriate durations - Don't delay too long unnecessarily
2. Consider timezones - Be aware of recipient timezones
3. Test delays - Verify delay behavior in test mode
4. Monitor executions - Check that workflows resume correctly

<a href="https://knowledge.captainbook.io/en/articles/13229969-delay-until-action">Delay Until Action</a>

<a href="https://knowledge.captainbook.io/en/articles/13230632-scheduled-time-trigger">Scheduled Time Trigger</a>

- <a href="https://knowledge.captainbook.io/en/articles/13229969-delay-until-action">Delay Until Action</a>
- <a href="https://knowledge.captainbook.io/en/articles/13230632-scheduled-time-trigger">Scheduled Time Trigger</a>

The Delay action pauses workflow execution for a specified duration. The workflow automatically resumes after the delay period.

Delay Action

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Delay Action

Overview

How It Works

Configuration

Duration (Required)

Use Cases

Examples

1. Follow-up Email

2. Reminder Sequence

3. Grace Period

Important Notes

Best Practices

Related Documentation