Klaviyo and Notion: Campaign Calendar Sync Template

This Spojit template keeps a shared campaign calendar in Notion up to date with your scheduled Klaviyo campaigns, on a recurring schedule.

What It Builds

A Schedule trigger fires on the cadence you choose (for example every morning). A Klaviyo Connector node lists the campaigns that are scheduled to send, and a Loop walks each one. Because Notion has no native tile, Spojit's http connector calls the Notion API to create or update a row in your campaign-calendar database, so the whole team sees send dates, subject lines, and statuses in one shared view.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

On a schedule every morning, list my scheduled Klaviyo campaigns and, for each one, create or update a page in my Notion campaign-calendar database (connect to the Notion API) with the campaign name, planned send date, subject line, audience, and status so my marketing team has one shared calendar.

Connectors Used

  • Schedule trigger - runs the sync on the cadence and time zone you set.
  • Klaviyo - lists the scheduled campaigns and their details.
  • http - Miraxa connects to the Notion API to write each campaign into your calendar database.

Customize It

Change the schedule cadence (hourly, twice daily, weekly), the Notion database you target, and which fields you map onto Notion properties. You can also tell Miraxa to include only campaigns sending in the next 14 days, or to add a Slack heads-up when a new campaign appears.

Tips

  • Give the Notion integration token write access to the target database, and have Miraxa match on campaign name or id so reruns update rather than duplicate rows.
  • Keep the Klaviyo lookup in Direct mode for a clean, no-AI-cost fetch; reach for Agent mode only if you want it to decide which campaigns qualify.
  • Set the Schedule trigger's time zone so send dates land on the right calendar day.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.