Skip to main content

Hey everyone, I created an app that integrates with Klaviyo via oauth and am struggling to extend its functionality to cover creation of flows via API.

I understand that the recommended approach is to first create the flow in UI, pull its definition, and then adjust it before creating an adjusted copy via API.

I do that but I am encountering a lot of problems and am struggling quite hard with this. Using zod schemas, trying my best to programatically ‘guess’ my way around API restrictions.

What just made it much more complicated is the fact that I started to hit some rate limits on my test account so it’s gotten impossible to test/iterate.

 

Does anyone have any proved approach that simply works when it comes to creating flows via API?
When can we expect some update to that part of the Klaviyo API?

Hey ​@rizze,

I hear your frustrations! Our team is always working to improve our API endpoints, and feedback like this will help us improve them in the future. If any other developers see this post, I’d love to get your thoughts on how you create flows via API and how you test them out/work around any obstacles you face with this!