Skip to main content
Delay is configured on each action. It determines how long that action waits after the preceding path becomes ready. There is no standalone Delay node.

​
Configuration Options

Set days, hours, and minutes within these ranges:
  • days: 0 to 365
  • hours: 0 to 23
  • minutes: 0 to 59
Email, call, Manual Task, profile view, connection request, LinkedIn message, and InMail actions support a delay.

​
LinkedIn Chat Timing

Consecutive LinkedIn messages and InMails on the same branch share one chat cadence. At least three cumulative hours must pass after the preceding chat action. The next chat action’s delay and delays from intervening blocking actions can combine to meet the three-hour minimum.

​
Manual Task Timing

A Manual Task’s delay holds the next action only when Wait for completion is enabled. In that mode, both the delay and task completion block progress. For a nonblocking Manual Task, its delay does not count toward the next action or the LinkedIn three-hour minimum.

​
Work Schedules

Delay expiration does not bypass a sender Work Schedule. If an email becomes ready outside its allowed window, it waits for the next eligible window. There is no Skip Weekends delay option; include or exclude weekend windows in the Work Schedule instead.