Last updated:
Monthly trigger
The Monthly trigger starts a dataflow automatically based on a monthly schedule.
When to use it
Section titled “When to use it”Use the Monthly trigger when a dataflow needs to run on specific months, specific days of the month, or based on a recurring weekday pattern (such as the third Wednesday of the month).
Typical use cases include:
- Monthly reporting
- Periodic billing or invoicing
Configuration
Section titled “Configuration”| Setting | Required | Description |
|---|---|---|
| Start | Yes | The date and time when the trigger becomes active and the first execution occurs. |
| Months | Yes | One or more months in which the dataflow should run (e.g. January, March, August). |
| Days | No | Specific calendar days of the month on which the dataflow should run (e.g. 1, 15, 31). |
| On | No | Alternative to Days. Allows scheduling based on a pattern such as First / Second / Third / Fourth / Last combined with a weekday (e.g. Third Wednesday). |
| Repeat every | No | Enables repeated execution within the selected day(s). The interval supports Seconds, Minutes, Hours, Days, and Weeks. |
| For duration of | No | Defines how long the repeated executions should continue. Can be set to Indefinitely or a specific duration in Seconds, Minutes, Hours, Days, or Weeks. |
| Random delay | No | Adds a random delay before execution. The delay value supports Seconds, Minutes, Hours, Days, and Weeks. |
- Use either Days or On, not both, to avoid ambiguous schedules.
- Limit repeat every usage unless multiple executions on the same day are required.
- Check the configured timezone before enabling the flow.