Flow action fields replaced and new trigger type added in Klaviyo API
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
In the flow action schema (appears to be EnrollFormAction or similar), expire_after_unit and expire_after_value have been removed and replaced by a new required field form_id (string). This is a breaking change for any client that reads or writes these fields, and form_id is now listed as required, so existing create/update calls omitting it will fail. Additionally, a new CustomObjectDateTrigger schema has been added and included as a valid option in the flow date trigger oneOf, which is purely additive.