Pre-Import options

Before importing templates, the file needs to be populated accordingly.

Recurring Task templates use the same columns as the standard Task import, so you can start from the Task import template (download it for an example in Tasks ⇒ Import). You don’t need to fill in Task dates, because the schedule determines when Tasks are created.

Setting the Schedule

The following columns can be used to set the schedule of the recurring Tasks:

Column	Description
`scheduleFrequency`	How often the schedule repeats: `WEEKLY` or `MONTHLY`.
`scheduleInterval`	The number of weeks or months between repetitions. For example, `2` with `WEEKLY` repeats every other week.
`scheduleWeekDays`	For weekly schedules: the days Tasks are due, separated by commas (e.g. `mon,wed,fri`).
`scheduleMonthDays`	For monthly schedules: the days of the month Tasks are due, separated by commas (e.g. `1,15`). Use `-1` for the last day of the month.
`scheduleStartDate`	Optional. The date the schedule begins, in YYYY-MM-DD format.
`scheduleEndDate`	Optional. The date the schedule ends, in YYYY-MM-DD format.
`scheduleCheckDay`	The day the schedule generates Tasks for the upcoming week or month. Use a weekday name for weekly schedules or a day of the month for monthly ones. Defaults to Monday (weekly) or the 1st (monthly).A

Importing Recurring Tasks

Importing Recurring Tasks can be done in Recurring ⇒ Import.

Click Import to open the Recurring Task import section, then upload the file containing the Tasks you want to import.

The CSV checker will automatically verify that all mandatory columns are filled in correctly. Once the file passes the check, click Next to continue.

Next, the addresses may need to be geocoded. This step is required unless you provided either UIDs (for example, for a depot or a customer and their location) or longitude and latitude for both the pickup and drop-off. On the Geocoding tab, select Geocode addresses. If any addresses fail validation, you can fix them manually by choosing an alternative result in the address lookup field.

In the configuration section, users can add tags if they wish. Click Next to proceed to the final step.

The Import step is the final step where you will see the number of Recurring Tasks that will be uploaded. To finalize, press Import.

Grouping Templates and Updating Template Groups

Rows with the same templateGroupUID are combined into a single recurring group that shares one schedule. If templateGroupUID is left empty, each row is treated as a separate group.

A few things to note in terms of template groups:

Schedule columns are ignored when templateGroupUID is provided. If a row includes a templateGroupUID field, any values specified in the following columns have no effect: scheduleFrequency, scheduleInterval, scheduleWeekDays, scheduleMonthDays, scheduleStartDate, scheduleEndDate, scheduleCheckDay, scheduleTaskDateRange, and keepAssignment. The import does not display a warning when it ignores these values.
Existing group settings remain unchanged. The import does not update the group's schedule, check day, or keepAssignment setting. It only adds the new Tasks to the existing group.
Schedules apply to groups, not individual Tasks. Tasks within a recurring group share the group's schedule rather than having individual schedules. As a result, no schedule is overridden when new Tasks are imported; they join the existing group and follow its schedule.

For example, imagine you have a group of Tasks that need to be executed every Mon, Wed, and Fri. A row is imported with that group's UID and scheduleWeekDays = tue. The new Task will be created on Mon, Wed, and Fri, following the group's set schedule, and Tuesday is ignored.

If a different schedule needs to be set, the following steps are required:

To change the schedule for the whole group, the group's schedule in the app must be edited.
To give the new Tasks their own schedule, import them without templateGroupUID. Fill in the schedule columns, and use templateGroupName to group rows that should share a schedule