Followup Tasks (Full Update)
Description
Upsert Followup Task Resource
See the Aerial Spec for more details.
File Naming Convention
TGEN_followupTasks_fullupdate_2026-08_<optionalSuffix>.csv
importType:fullupdateapiVersion:2026-08
Columns
Nested object fields are flattened into columns using dot notation (parent.child). Array fields are flattened using zero-based index notation, one element per column (field[0], field[1], and so on).
Note: A whole array cannot be passed in a single column: a literal value such as ['value-1','value-2'] will be rejected. To import multiple array elements, add one indexed column per element. Rows in the table below with type array describe the field as a whole and are not valid CSV column headers.
| Column Header | Description | Key Information | Type | Required |
|---|---|---|---|---|
externalId | External ID of the followupTask | Max Length: 255 | string | No |
title | Title of the task | Max Length: 255 | string | Yes |
description | Description of the task | string | No | |
status | Status of this follow up | Allowed: ACTIVE, IGNORED, COMPLETED, INACTIVE | string | Yes |
assignedEmployee | Employee to whom this task is assigned | string | No | |
assignedByEmployee | Employee who assigned this task | string | No | |
createdByEmployee | Employee who created this task | string | No | |
customer | Customer associated with this task | string | No | |
store | Store to which this task belongs - required if assignedEmployee is not supplied. | string | Yes | |
campaign | Campaign to which this task belongs. | string | No | |
taskType | Type of followup, see crm/taskTypes API | string | Yes | |
dateDue | Datetime of when the followup task is due in Z-normalized RFC3339 format | string | Yes |
Sample CSV
See the following followupTasks CSV sample file.
Note: The sample CSV may contain sample ID fields which reference other resources that do not match the data in your environment.