One-time or recurring execution
The trigger At a defined time allows you to automatically run an automation at a single moment or at a specific frequency, according to a configurable schedule.
➡️ How it works
This trigger allows you to schedule actions without manual intervention, using a view filter.
It is useful for background tasks, scheduled sends, or maintenance routines.
➡️ Select a view on which the recurring action will be applied.
You can schedule these tasks based on :
⬇️ Configuration parameters
➡️ Hourly scheduling
This setup allows you to run an automation every X hours, on a regular basis.
Time unit — Hours
Define the hourly interval between each execution.
Allowed range: between 1 and 23 hours
Example: every 2 hours
ℹ️ This setting is ideal for:
Regularly updating data
Performing hourly synchronizations
Checking the status of sensitive fields
➡️ Daily scheduling
2️⃣ Every [X] days
Define the repetition interval in days.
Example: every 3 days
3️⃣ At the following time
Specify the exact time (UTC) at which the automation should run.
➡️ Format: HH:MM
Example: 06:30 to run each morning at 6:30.
➡️ Weekly scheduling
1️⃣ Only on one or more days of the week (e.g. Tuesday and Thursday).
2️⃣ Each weekday (Monday to Friday).
3️⃣ Each weekend (Saturday and Sunday).
➡️ Allows you to define the exact time of execution (e.g. 08:00 every morning at 8am).
➡️ Monthly scheduling
1️⃣ Only for certain months – choose specific months (e.g. January, June, December).
2️⃣ Every month – runs monthly without distinction.
3️⃣ On the Xᵗʰ day of the month – select a day (e.g. 1st, 15th, or 28th).
4️⃣ On the last day of the month – runs only on the last day, regardless of month length.
5️⃣ On the last working day of the month – runs on the last weekday (excluding Saturday and Sunday).
➡️ Define the exact time of execution (e.g. 00:00 to run at midnight UTC).
ℹ️ Notes
This trigger is independent of user actions: it works even without activity in the database.
A well-filtered view allows you to restrict the action to the relevant rows only.
It is ideal for automated sends, synchronizations, or regular data cleaning.