PATCH /client/workflows/{workflow_id}/customization to apply these fields.
Timing fields
delay_minutes
Type: integer
The number of minutes to wait after a contact triggers the workflow before the email is scheduled.
This is a minimum wait — not necessarily the final send time. After the delay elapses, the scheduler applies send_time_mode to find the next valid send window.
Example: delay_minutes = 120, send_time_mode = 1 — contact triggers at 9:00 AM → earliest scheduling attempt is 11:00 AM → scheduler picks the next valid window at or after 11:00 AM.
If not set, the workflow’s system default is used.
send_time_mode
Type: integer (enum)
Controls exactly when the email is sent once the delay has elapsed.
For send windows and allowed weekday configuration, see Send windows and timezones.
preferred_send_hour
Type: integer (0–23)
Hour of day in the contact’s local timezone to send the email.
Only used when send_time_mode = 3. Must be set together with preferred_send_minute.
preferred_send_minute
Type: integer (0–59)
Minute within the hour to send the email.
Only used when send_time_mode = 3. Must be set together with preferred_send_hour.
Priority field
priority_score
Type: integer (1–100)
Controls queue processing order for this workflow relative to others. Higher score means the workflow’s emails are processed sooner when multiple sends are queued at the same time.
Overrides the workflow’s system default priority score.
Full customization request example
What you cannot change
MailerPath controls the following and they are not client-customizable:- Entry and exit conditions
- Suppression and conflict rules
- Workflow step sequence and logic
- Template structure and copy (except through template editing)