Klaviyo Weekly Campaign Report to Slack with Kestra

id: klaviyo-campaign-performance-report
namespace: company.marketing

labels:
  team: marketing
  report: klaviyo-weekly

inputs:
  - id: campaign_ids
    type: ARRAY
    itemType: STRING
    description: |
      Klaviyo campaign IDs to include in the weekly performance report. Update
      this list each cycle (or wire a discovery step in front of this flow) so
      the report covers the campaigns that actually sent in the window. The IDs
      below are placeholders.
    defaults:
      - "01HXXXXXXXXXXXXXXXXXXXXXXX"
  - id: statistics
    type: ARRAY
    itemType: STRING
    description: |
      Klaviyo campaign-values statistics to request from the reporting API.
      These are the real performance KPIs that drive the report.
    defaults:
      - opens
      - open_rate
      - clicks
      - click_rate
      - delivered
      - bounced
      - unsubscribes
      - conversion_value
  - id: conversion_metric_id
    type: STRING
    description: |
      Klaviyo conversion metric ID used by the campaign-values report (for
      example the "Placed Order" metric ID from your account). Required by the
      reporting endpoint to attribute revenue. Replace the placeholder.
    defaults: "RESH2Z"

pluginDefaults:
  - type: io.kestra.plugin.klaviyo
    values:
      apiKey: "{{ secret('KLAVIYO_API_KEY') }}"
  - type: io.kestra.plugin.slack.notifications.SlackIncomingWebhook
    values:
      url: "{{ secret('SLACK_WEBHOOK_URL') }}"

variables:
  window_end: "{{ (trigger.date ?? execution.startDate) | date('yyyy-MM-dd') }}"
  window_start: "{{ (trigger.date ?? execution.startDate) | dateAdd(-7, 'DAYS') |
    date('yyyy-MM-dd') }}"

tasks:
  - id: get_campaigns
    type: io.kestra.plugin.klaviyo.campaign.Get
    description: Fetch the selected campaigns so the report can show name and status per ID.
    campaignIds: "{{ inputs.campaign_ids }}"
    fetchType: FETCH
    retry:
      type: constant
      interval: PT30S
      maxAttempt: 4
    timeout: PT10M

  - id: campaign_values_report
    type: io.kestra.plugin.core.http.Request
    description: |
      Pull real per-campaign KPIs (opens, clicks, delivered, revenue) from the
      Klaviyo Campaign Values Reporting API for the report window. This is the
      data that makes the report a performance report rather than a row count.
    uri: https://a.klaviyo.com/api/campaign-values-reports
    method: POST
    contentType: application/json
    headers:
      Klaviyo-API-Key: "{{ secret('KLAVIYO_API_KEY') }}"
      revision: "2024-10-15"
      accept: application/json
    body: |
      {{ {
        "data": {
          "type": "campaign-values-report",
          "attributes": {
            "statistics": inputs.statistics,
            "timeframe": {
              "start": render(vars.window_start) ~ "T00:00:00",
              "end": render(vars.window_end) ~ "T00:00:00"
            },
            "conversion_metric_id": inputs.conversion_metric_id,
            "filter": "any(campaign_id," ~ (inputs.campaign_ids | join(",")) ~ ")"
          }
        }
      } | toJson }}
    options:
      readTimeout: PT2M
    retry:
      type: constant
      interval: PT30S
      maxAttempt: 4
    timeout: PT10M

  - id: write_metrics_json
    type: io.kestra.plugin.core.storage.Write
    description: |
      Project the reporting API response into a flat JSON array (one row per
      campaign with its KPIs) so it converts cleanly to Ion and CSV. The raw
      JSON:API response has nested attributes/relationships that do not flatten,
      so we extract the result groupings here first.
    extension: .json
    content: "{{
      fromJson(outputs.campaign_values_report.body).data.attributes.results |
      toJson }}"

  - id: metrics_to_ion
    type: io.kestra.plugin.serdes.json.JsonToIon
    description: Convert the flat metrics JSON array to Ion for CSV serialization.
    from: "{{ outputs.write_metrics_json.uri }}"
    newLine: false

  - id: metrics_to_csv
    type: io.kestra.plugin.serdes.csv.IonToCsv
    description: Convert the flat per-campaign KPI rows to a CSV for archiving or BI
      ingestion.
    from: "{{ outputs.metrics_to_ion.uri }}"

  - id: notify_summary
    type: io.kestra.plugin.slack.notifications.SlackIncomingWebhook
    description: Post the weekly performance summary with real KPIs and the report window.
    payload: |
      {
        "blocks": [
          {
            "type": "header",
            "text": {
              "type": "plain_text",
              "text": "Klaviyo weekly campaign report"
            }
          },
          {
            "type": "section",
            "fields": [
              {
                "type": "mrkdwn",
                "text": "*Report window:*\n{{ vars.window_start }} to {{ vars.window_end }}"
              },
              {
                "type": "mrkdwn",
                "text": "*Campaigns reported:*\n{{ outputs.get_campaigns.size ?? 0 }}"
              },
              {
                "type": "mrkdwn",
                "text": "*KPI rows:*\n{{ (fromJson(outputs.campaign_values_report.body).data.attributes.results | length) ?? 0 }}"
              },
              {
                "type": "mrkdwn",
                "text": "*Execution:*\n{{ execution.id }}"
              }
            ]
          },
          {
            "type": "context",
            "elements": [
              {
                "type": "mrkdwn",
                "text": "A CSV of per-campaign KPIs (opens, clicks, delivered, revenue) is attached to this Kestra execution. Open the run to download it."
              }
            ]
          }
        ]
      }

errors:
  - id: alert_on_failure
    type: io.kestra.plugin.slack.notifications.SlackIncomingWebhook
    description: Alert the channel if the report run fails so a missed Monday report
      is never silent.
    messageText: ":rotating_light: {{ flow.namespace }}.{{ flow.id }} failed
      (execution {{ execution.id }})."

triggers:
  - id: weekly_report
    type: io.kestra.plugin.core.trigger.Schedule
    description: Build and post the report every Monday at 08:00 UTC.
    cron: "0 8 * * 1"
    timezone: Etc/UTC

Automate a recurring Klaviyo email marketing performance report with Kestra. Every week this flow fetches your selected Klaviyo campaigns, pulls real per-campaign KPIs (opens, open rate, clicks, click rate, delivered, bounced, unsubscribes, and attributed conversion revenue) from the Klaviyo Campaign Values Reporting API, exports the metrics to a clean CSV for archiving or BI ingestion, and posts a performance summary to Slack. It solves the recurring problem of marketers manually exporting campaign analytics from the Klaviyo dashboard each week: instead you get a scheduled, reproducible, hands-off report with the actual engagement and revenue numbers, not just a row count.

How it works

The weekly_report Schedule trigger (io.kestra.plugin.core.trigger.Schedule) fires every Monday at 08:00 UTC. The window_start and window_end variables derive a seven-day window from the trigger date (or the execution start date on a manual run), so backfills compute the correct window.
get_campaigns (io.kestra.plugin.klaviyo.campaign.Get) fetches the campaigns listed in the campaign_ids input so the report knows each campaign's name and status.
campaign_values_report (io.kestra.plugin.core.http.Request) POSTs to the Campaign Values Reporting endpoint, requesting the KPIs in the statistics input for the window, scoped to the selected campaigns and attributed against conversion_metric_id.
write_metrics_json (io.kestra.plugin.core.storage.Write) projects the JSON:API response into a flat array, then metrics_to_ion (io.kestra.plugin.serdes.json.JsonToIon) and metrics_to_csv (io.kestra.plugin.serdes.csv.IonToCsv) convert it to a clean CSV.
notify_summary (io.kestra.plugin.slack.notifications.SlackIncomingWebhook) posts the window, campaign count, KPI row count, and execution id to Slack.

What you get

A CSV of per-campaign KPIs (opens, clicks, delivered, attributed revenue) attached to each execution, ready for archiving or BI.
A weekly Slack summary with the report window, campaigns reported, and KPI row count.
A reproducible, scheduled report that runs without anyone opening the Klaviyo dashboard.

Who it's for

Email and lifecycle marketers who report Klaviyo performance on a weekly cadence.
Marketing ops and analytics engineers who need campaign KPIs landed as CSV for downstream BI.
Growth teams that want revenue-attributed campaign metrics surfaced in Slack automatically.

Why orchestrate this with Kestra

Klaviyo's own scheduling cannot pull a multi-campaign reporting export, flatten the JSON:API payload, and broadcast it to Slack on a cron. Kestra adds an event-driven Schedule trigger, per-task retries (constant, 4 attempts, 30s apart) and 10-minute timeouts so a transient 429 or 5xx self-heals, an errors block that alerts Slack if the run fails so a missed Monday report is never silent, full execution lineage and downloadable artifacts, and declarative YAML you can version control. Shared credentials live once in pluginDefaults instead of being repeated on every task.

Prerequisites

A Klaviyo account with a Private API Key that has read access to campaigns and campaign reporting (analytics).
The conversion metric ID used for revenue attribution (for example the "Placed Order" metric ID from your account).
A Slack incoming webhook pointing at the channel that should receive the report.

Secrets

KLAVIYO_API_KEY: Klaviyo Private API Key, sent as the Klaviyo-API-Key header by the Klaviyo task and the reporting HTTP call.
SLACK_WEBHOOK_URL: Slack incoming webhook URL used to post the summary and any failure alert.

Quick start

Add the KLAVIYO_API_KEY and SLACK_WEBHOOK_URL secrets to your Kestra namespace.
Set the campaign_ids input to the campaigns you want to report on and conversion_metric_id to your account's conversion metric.
Adjust the statistics input if you want a different KPI set.
Enable the flow and let the Monday schedule run it, or trigger it manually to test.

How to extend

Add a discovery step in front of the flow that lists campaigns sent in the last seven days and feeds their IDs in, so the report stays current without manual edits.
Change the weekly_report cron for a daily or monthly cadence.
Push the CSV to S3, GCS, or a warehouse, or load the flat metrics straight into BigQuery or Snowflake for dashboards.
Branch the Slack summary on thresholds (for example, alert when open rate drops below a target).

Weekly Klaviyo Campaign Performance Report to Slack

How it works

What you get

Who it's for

Why orchestrate this with Kestra

Prerequisites

Secrets

Quick start

How to extend

Links

Tasks

Orchestrate with Kestra

Share this Blueprint

Create a Blueprint

New to Kestra?

Weekly Klaviyo Campaign Performance Report to Slack

How it works

What you get

Who it's for

Why orchestrate this with Kestra

Prerequisites

Secrets

Quick start

How to extend

Links

Tasks

Orchestrate with Kestra

Share this Blueprint

Create a Blueprint

More Business Blueprints

AI-Powered Stock Watchlist Analysis with Daily Alerts and PostgreSQL Logging

Convert Natural Language Prompts to Structured Todoist Tasks with Deepseek AI

Generate and Deliver an AI-Powered Daily News Digest from RSS Feeds via Slack and Email

AI-Powered Inventory Demand Forecasting, Auto-Generate Purchase Orders with OpenAI

Query and filter customer data from HubSpot

Generate AI Blog Posts in Your Brand Voice and Publish to WordPress as Draft

New to Kestra?