[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-klaviyo-openapi-2026-05-19-flow-action-fields-replaced-and-new-trigger-type-added-in":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"klaviyo-openapi","Klaviyo API","klaviyo","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fklaviyo\u002Fopenapi\u002Fmain\u002Fopenapi\u002Fstable.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KS08M9BPXQFCSB7YJVQNSZZG","2026-05-19-flow-action-fields-replaced-and-new-trigger-type-added-in","Breaking","Flow action fields replaced and new trigger type added in Klaviyo API","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\u002Fupdate 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.","2026-05-19T14:00:55.926Z"]