The layout is a JSON with the necessary information to send the messages. The variables should be enclosed in double curly braces (ex: {{variable}}).

The only required fields are contactCode and channelType (inside the contact object).

Optionally, you can use the 'customFields' property to define which columns in the CSV correspond to the variables used in the campaign to be sent.

Other fields like sendType or messageContent are defined in the campaign, so you don't need to define them in the layout.

An examples of layouts:

Example 1: using both contact variables and custom fields

{
  "contact": {
    "contactCode": "{{contactCode}}",
    "channelType": "{{channelType}}"
  },
  "customFields": { 
      "name": "{{nombre}}",
      "ticketId": "{{ticket_id}}",
      "age": "{{edad}}"
  }
}

Example 2: It's not necessary to define a variable for the channelType property (if all recipients belong to the same channel). It's also not required to define the customFields property if the campaign doesn't have variables.

{
  "contact": {
    "contactCode": "{{contactCode}}",
    "channelType": "cloud_api"
  }
}

Example 3: you can use other names for the variables

{
  "contact": {
    "contactCode": "{{phoneNumber}}",
    "channelType": "{{channel}}"
  },
  "customFields": { 
      "name": "{{nombre_cliente}}",
      "age": "{{edad_cliente}}"
  }
}

Example 4: It's not mandatory to define variables for custom fields; you can use fixed values instead.

{
  "contact": {
    "contactCode": "{{contactCode}}",
    "channelType": "{{channelType}}"
  },
  "customFields": { 
      "name": "Dear client",
      "discount": "10%"
  }
}

The delay before sending the messages. The use of this property will schedule the sending of the messages to be sent after the specified delay from the current time.

This property can not be used in conjunction with the scheduleAt property.

The format must be in ISO 8601 duration.

Examples:

• PT0.25S for 250 milliseconds
• PT20S for 20 seconds
• PT15M for 15 minutes
• PT30M50.5S for 30 minutes, 50 seconds and 500 milliseconds
• PT4H for 4 hours
• P3D for 3 days
• P2W for 2 weeks
• P1M for 1 month

The slicing condition allows you to define how the messages should be sliced when sending them.

• fragmentedSlots: If slicing is enabled, slots will be assigned based on availability starting from the scheduled time, regardless of whether they are consecutive, and only within the next 48 hours.
• immediateConsecutiveSlots: If slicing is enabled, slots will be assigned based on availability starting from the current time (or from the scheduled time, if it's a scheduled sending), and within the next 48 hours — but only if they are consecutive. If not enough consecutive slots are found, the task will be marked as canceled and will not be executed.
• deferredConsecutiveSlots: If slicing is enabled, the system will attempt to find a set of consecutive available slots starting from the scheduled time and within the next 48 hours. If no suitable slots are found, the task will be marked as canceled and will not be executed.

If not provided, the default condition is fragmentedSlots.

Keep in mind that these conditions will only apply to a given sending when the slicing activation criteria are met.