The “Schedule” node, an action type, is used to schedule actions that need to be performed regularly within a workflow.
Its use allows you to define how often an action should repeat, at what time of day it should execute, and when it should stop repeating for each contact. This is useful for creating recurring strategies, such as periodic sends, reminders, or scheduled communications.
How to Access?
Within the workflow editor, drag the “Schedule” node from the right menu to the design area. You can access its settings by clicking (Edit node settings).
Interface
The main interface of the "Schedule" node consists of 4 blocks:
- Periodic scheduling parameters: to configure how often the action will repeat. It allows defining whether the scheduling will be daily, weekly, or monthly.
- Time scheduling parameter: to indicate at what time of day the action will execute according to the configured periodic schedule.
- Node completion parameter: to define whether the scheduling should end at a certain time or remain active indefinitely for each contact.
- Execution reset upon new events: to define how the node behaves when the same contact passes through it again as a result of a new workflow execution.
How It Works
Action-type nodes perform specific operations within flows. The “Schedule” node allows temporarily pausing a contact's progression until the configured schedule is met and, from that point, lets the contact continue to the next nodes in the workflow.
Unlike the “Wait” node, which establishes a one-time pause, the “Schedule” node allows scheduling recurring actions, such as daily, weekly, or monthly sends.
The action following the node will execute when the configured frequency and time are met. Additionally, the scheduling can be limited to a set number of repetitions or remain active indefinitely, depending on the configuration.
1. Configure the Action Frequency
In the Periodic scheduling parameters (1), select how often the action will be scheduled. You can choose from:
- Daily: to repeat the action every day or every certain number of days. For example, every two days.
- Weekly: to define how many weeks between repetitions and on which day(s) of the week. For example, every two weeks on Mondays, Wednesdays, and Fridays.
- Monthly: to define how many months between repetitions and which day(s) of the month. For example, every two months on the 1st, 15th, and 30th of that month.
The example shows a schedule that runs every three months, on the 1st and 15th of that month.
2. Define the Execution Time
In the Time scheduling parameters (2), specify the time you want the scheduled action to execute. This scheduling ensures the action is planned at the determined time within the chosen frequency.
The example shows a schedule that runs every three months, on the 1st and 15th of that month at 9:00 am.
3. Configure When the Scheduling Should End
In the Node completion parameter (3), define whether the scheduling should end after a set number of repetitions or remain active indefinitely.
In this node, one repetition occurs each time the configured schedule is met, allowing contacts within it to advance to the next workflow nodes.
The number of contacts advancing in each repetition does not count toward the maximum number of repetitions configured.
The example shows a schedule that runs every three months, on the 1st and 15th of that month at 9:00 am. The scheduling will end once it has executed 1,000 times.
4. Define Behavior for New Events
In Execution reset upon new events (4), specify how Connectif should count the times the same contact passes through the “Schedule” node again due to a new workflow execution.
If this option is disabled, Connectif will accumulate the number of times the contact has passed through the node. That is, if a contact enters multiple times, it will be counted as a cumulative sequence: 1, 2, 3, 4, etc.
If this option is enabled, Connectif will reset that count each time the contact passes through the node again. Thus, instead of accumulating previous entries, each new entry will be counted again from 1.
This option is useful when you don’t want to analyze the total accumulated times a contact has passed through the node but rather identify each new entry independently.
The example shows a schedule that runs every three months, on the 1st and 15th of that month at 9:00 am. The scheduling will end once it has executed 1,000 times.
Congratulations!
You have reached the end of the lesson.
Still have unanswered questions?
Remember that our Connectif specialists are available to help you. To contact them, simply open a Support ticket by clicking the blue “Help” button on your dashboard.
Keep Learning!
To fully leverage your Connectif account’s potential, we recommend continuing with the following articles:
Weekly Campaign with Personalized Product , to create a weekly campaign with a personalized product.
Reactivation of Seasonal Buyers , to create a strategy for reactivating seasonal buyers.
Action Type Nodes , to perform specific operations within flows.
Connectif Copilot , to learn about the assistant’s functionality and interface.