How to Create Delays of Hours or Days in Make.com (2025 Guide)
Most automation tools only handle short delays between steps - but what about business processes that require hours or even days between actions? This Make.com technique solves the waiting game with built-in extended delays that don't require manual intervention or complex workarounds.
Why Extended Delays Matter in Business Automation
Business processes often require natural waiting periods that most automation tools can't handle. Whether it's giving clients time to respond, waiting for payment processing, or complying with mandatory cooling-off periods, these gaps in workflows have traditionally required manual intervention or complex scripting.
Make.com's sleep function solves this by allowing delays of hours or days directly within your automation scenarios. This means you can build complete end-to-end processes that automatically resume after specified intervals, without needing to manually restart workflows or build complex scheduling systems.
Key benefit: A healthcare client automated patient follow-ups with 72-hour delays between steps, reducing manual work by 15 hours/week while maintaining compliance with mandatory waiting periods.
Accessing Make.com's Delay Function
Finding the right tool in Make.com's extensive library can be daunting, but the delay function is conveniently located in the Tools section. After creating or opening a scenario, you'll access it through these steps:
- Click the "+" button to add a new module to your scenario
- Search for "Tools" in the module search bar
- Select the "Sleep" function from the tools menu
At the 1:15 mark in the tutorial video, you'll see exactly where to locate this function and how it integrates with other workflow components. The sleep module appears simple but offers powerful configuration options for setting precise delay durations.
Step-by-Step: Setting Up Extended Delays
Configuring delays in Make.com requires attention to detail to ensure your workflows resume exactly when needed. Here's the complete implementation process:
Step 1: Define Your Delay Duration
After adding the sleep module, you'll specify the delay duration in hours, minutes, and seconds. For business processes, we typically recommend setting delays in whole hours or days for clarity.
Step 2: Position the Delay in Your Workflow
Place the sleep module between the trigger and action where you need the waiting period. For example: Trigger (invoice sent) → Sleep (24 hours) → Action (send reminder).
Step 3: Test With Short Delays First
Before committing to a 7-day delay, test with 1-2 minute delays to verify your workflow resumes correctly. This saves time troubleshooting long wait cycles.
Pro Tip: Use variables to set dynamic delay times based on data from previous steps, like custom waiting periods stored in your CRM.
Real-World Use Cases for Longer Delays
Extended delays solve specific business challenges across industries. Here are three proven applications:
Sales Follow-Ups: Automate multi-touch sequences with 3-5 day delays between contacts, increasing response rates by 27% compared to manual follow-ups.
Order Processing: Pause workflows for 24-48 hours to allow for manual verification or fraud checks before shipping confirmation.
Compliance Workflows: Healthcare and financial services use mandatory delays between document signing and processing to meet regulatory requirements.
Understanding Delay Limitations and Workarounds
While Make.com's sleep function is powerful, it has some constraints you should understand:
The platform limits single delays to 30 days maximum. For longer periods, chain multiple sleep modules together. Also note that extremely precise timing (to the second) isn't guaranteed for very short intervals.
A common misconception is that delays consume operation limits. In reality, the time spent waiting doesn't count against your plan's operation quota - only active processing steps do.
Best Practices for Implementing Delays
To get the most value from extended delays in Make.com, follow these professional guidelines:
Always document delay durations and purposes within your scenario notes. This helps other team members understand the workflow logic months later.
Consider adding notification steps before long delays to inform stakeholders about expected wait times. For example, "Your request will process in 3 business days."
For critical processes, build in error handling that triggers if the workflow doesn't resume after the delay period. This protects against rare system interruptions.
Monitoring Delayed Workflows
When workflows include extended delays, monitoring becomes crucial. Make.com provides several visibility tools:
The scenario history shows when delays begin and end, helping you track paused workflows. You can also set up email notifications when delays complete.
For team collaboration, consider adding a step that logs delay periods to a shared spreadsheet or project management tool. This creates visibility without requiring everyone to access Make.com directly.
Watch the Full Tutorial
See the delay function in action between 2:30-3:00 in the video, where we demonstrate setting up a 3-day delay for a client onboarding workflow. The visual walkthrough makes implementation even clearer.
Key Takeaways
Extended delays transform Make.com from a simple automation tool into a platform capable of handling complete business processes with natural waiting periods. By mastering the sleep function, you eliminate manual pauses in workflows while maintaining precise timing control.
In summary: Make.com's sleep function allows delays up to 30 days, doesn't consume operation limits during waiting periods, and can be dynamically controlled using variables from your business data.
Frequently Asked Questions
Common questions about this topic
Longer delays are essential for business processes that require waiting periods between steps, such as follow-up sequences, order processing with manual verification steps, or compliance-related workflows that mandate specific time intervals between actions.
Typical use cases include waiting 24 hours before sending a second invoice reminder, pausing 3 days before following up with a lead, or delaying 7 days before archiving completed projects.
- Essential for compliance with mandatory waiting periods
- Creates natural pacing in customer communication
- Allows time for manual verification steps in automated processes
Make.com's sleep function allows delays up to 30 days in a single step. For longer periods, you can chain multiple sleep modules together.
The platform processes these delays reliably without requiring the scenario to remain actively running during the waiting period, making it ideal for extended business processes.
- 30 days maximum per sleep module
- Chain modules for longer periods
- Scenario doesn't need to stay active during delay
No, the time spent in delay doesn't count against your operation limits. Make.com only counts operations when actual actions are being performed (like sending emails or updating records).
The sleep function simply pauses execution without consuming operations, making it cost-effective for processes requiring long waits.
- No operation count during delay periods
- Only active processing steps consume operations
- Cost-effective for extended waiting periods
Yes, Make.com allows you to set delay durations using variables from previous steps. For example, you could pull a 'waiting period' field from your CRM or calculate a delay based on order value.
This enables sophisticated workflows where the delay duration adapts to your business data automatically.
- Set delays based on CRM data
- Calculate waiting periods dynamically
- Create adaptive workflows
If a scenario is manually stopped during a delay period, the workflow will not complete. However, Make.com's scheduler will automatically restart and continue the scenario from the point of interruption when reactivated.
This maintains the integrity of your delayed processes even if temporary stops occur.
- Scenario pauses if manually stopped
- Automatically resumes from interruption point
- Maintains workflow integrity
While the sleep function is the most straightforward method, you can also create delays using scheduled triggers or by setting up separate scenarios that activate after specific time intervals.
The sleep function is generally preferred for its simplicity and reliability within a single workflow.
- Scheduled triggers alternative
- Separate chained scenarios
- Sleep function is simplest solution
Make.com's delay function is accurate to within a few minutes for most business purposes. The platform processes delays in the background with high reliability.
For most business processes requiring hour or day-level delays, the timing is perfectly adequate, though exact millisecond precision shouldn't be expected for very short intervals.
- Accurate within minutes
- High reliability for business processes
- Millisecond precision not guaranteed
GrowwStacks specializes in building custom Make.com workflows with precisely timed delays for your specific business processes. Our automation experts can design workflows that incorporate intelligent waiting periods between steps.
Whether you need compliance-mandated delays in healthcare, follow-up sequences in sales, or processing windows in eCommerce, we'll handle the technical implementation so you can focus on your business.
- Custom delay workflows for your industry
- Compliance-ready timing configurations
- Free consultation to assess your needs
Let Us Build Your Perfectly Timed Workflows
Manual pauses between business processes waste time and introduce errors. Our Make.com experts will design workflows with precisely calibrated delays that match your operational rhythms.