How can I automatically send an email for each new blog post with the title and content of the post ?

​@sperezclavier 

The URL is the Klaviyo API endpoint that you’re trying to use, as I linked to in the numbered list 1-3 above. Although, a year has gone by so some of those endpoints may have changed.

What do you mean, “if a datapoint is nested”? Are you talking about the JSON body? Each endpoint in the API has example JSON bodies that you can copy/paste into the Zapier webhook body. You just need to update the fields with the dynamic data from previous steps in the zap.

If you want more specifics, your questions will have to be more specific too. The Klaviyo API links I’ve already posted go to the specific endpoint and the screenshot shows the specific setup in Zapier. 

What David was specifying was using Zapier to trigger the flow since Klaviyo doesn’t offer an auto recurring trigger that integrates with Wordpress post actions. 

However, we needed a bit more customization in addition to triggering the flow:

• We needed to schedule the emails to send no more than once a week, and then only if a new post had been published at that time.
• The email needed to include dynamic images. 

So for whom it may help, I’ve put together an overview of how we accomplished this with a (paid) Zapier account and Klaviyo:

NOTE: The limitation when using Klaviyo - beyond the inability to trigger a flow based on blog updates - it does not currently support RSS feed dynamic images, only text content. Because of that, we need to collect the RSS feed in Zapier before passing it as a custom event to Klaviyo to trigger the flow and provide the image content. 

1. First, we add a simple php function to add the featured image to RSS feed in Wordpress since it doesn’t support it by default.
2. Second, we create a “test bot” in Zapier to send our custom event data to Klaviyo and create our custom event for the first time. - This step is needed because Klaviyo only adds the custom event Trigger once an initial webhook event has been received. 
3. Third, in Klaviyo, we create a new flow triggered by the custom event we sent via Zapier in the previous step. We further filter this flow to only send to subscribers on a specific list.
4. Fourth, with our trigger in place, we add a new email to show our dynamic content. We’ll add the content later, but for now we’ll publish the flow “Live”.
5. Fifth, in Zapier now, we create a new Zap with multiple steps: First we use a Schedule trigger to automatically run our Zap weekly. Next, we collect the XML feed from our website, and pass it through as raw data. Next we have an updates checker to see if the XML feed has been updated in the past week. If yes, the Zap continues to the Extraction stage, where we pull the featured image URL, post title, and post link out of the raw feed for the final stage. Last we send our custom event template from Step 2, now mapped with the dynamic payload from our XML feed, to Klaviyo. This will trigger the flow and deliver the data we’ll add to our dynamic content email. 

Once Zapier has been fully setup and tested, we can now return to Klaviyo and edit the flow’s email template to add our custom dynamic variables. Note that you will NOT be able to utilize the Dynamic Feed table options here - instead add the new custom variables as {{ event.yourcustomfieldhere }} in the source code.

• For the images, use the Dynamic images option or embed with html for better manual styling control. 
• Use the “Preview” option to see what variable are being received from Zapier then grab the specific dynamic links you need to build your content. 

Finally, you can test the entire system by manually running the Zapier trigger to ensure your flow is being triggered in Klaviyo and that you get the flow email with the dynamic feed showing correctly. Turn off the “Smart Send” option for this flow to avoid conflicting send rules.

Final note: this is a developer level integration, not very beginner friendly.