Course Content
Flows – Expert
0/8
The Sleep Node – AI Agent
00:00
The Run Flow Action – AI Agent
00:00
The Table Node – AI Agent
00:00
Filtering a table – AI Agent
00:00
Setting Up an Event Trigger – AI Agent
00:00
Filtering Records for a Trigger – AI Agent
00:00
Using Values from the Trigger – AI Agent
00:00
Course Exercise: Creating a Monday Account Automatically based on Salesforce – AI agent
00:00
Flows – Expert

Lesson Guide: Managing API Rate Limits with the Sleep Node

In this lesson, you will learn how to optimize your automated processes using the Sleep Node in Noca Flow. When dealing with external software systems (such as CRMs, ERPs, or databases), you will often encounter rate limiting—a strict limit on how many records you can create or update within a short timeframe.

By inserting controlled, timed pauses directly into your record loops, you can safely space out heavy data processing tasks and prevent your automation from crashing due to system restrictions.

Step 1: Open Your Loop and Locate the Target Action

To prevent hitting API speed limits, the timed delay needs to happen right before your flow pushes data to an external service.

  1. Open your existing Loop automation canvas from the previous lesson.

  2. Locate the Salesforce Object Update Node (or any action node hitting an external database) nestled inside your loop wrapper.

  3. Hover your mouse over the incoming path connection directly preceding that update node.

Step 2: Insert the Sleep Node

The Sleep Node can be dropped anywhere in a workflow path where a physical delay is required.

  1. Click the + icon on the path right before your Salesforce Update Node.

  2. In the “Add Node” search panel, type sleep.

  3. Select the Sleep Node and click Insert.

Step 3: Configure the Time Delay Length

Once placed on the canvas, you need to define exactly how long the workflow engine should hold its breath before proceeding.

  1. Click on the newly added Sleep Node to view its property settings on the right panel.

  2. Locate the Time input field.

  3. Enter your desired wait duration in seconds (e.g., enter 10 to configure a strict 10-second delay).

💡 Why inside the loop? Because this node is nested inside a loop canvas, it will dynamically execute sequentially. If your loop is handling 13 records, Noca will systematically sleep for 10 seconds, update a record, loop back, sleep for another 10 seconds, and update the next record.

Step 4: Save, Run, and Monitor the Live Delay

  1. Click Save and Run in the top navigation bar.

  2. Open the Timeline and live debugging drawer on the right side of your screen to monitor the execution trail.

  3. Watch the Clock: You will see the manual trigger fire, the record collection pull instantly, and the loop begin. The trail will hit the Sleep Node and gracefully pause.

  4. Check the live log timestamps—Noca will freeze processing for exactly 10 seconds before lighting up the Salesforce update action, successfully ensuring your application spaces out its transaction load perfectly.

Key Takeaways

  • Bypassing Rate Limits: The Sleep Node is your primary defense against target systems throwing 429 Too Many Requests API errors.

  • Interval Spacing: Placing a Sleep Node inside a loop structure compounds the delay, executing the pause over every individual iteration to guarantee safe data spacing.

Fantastic job! You now know how to design flows that are not only logically smart, but database-responsible and stable at scale. What system integrations are you planning to optimize next? Turn to our community channels to share your build goals!

Previous
Next