Klaviyo automations

If you run two or more integrations — say Zapier for order triggers and n8n for CRM sync — both using private API keys on the same Klaviyo account, they draw from a shared rate limit pool. At peak hours, one integration's burst can silently exhaust the quota for the other, causing 429 errors that look like isolated failures but are actually cross-contamination. The fix is to migrate at least one integration to OAuth, which gives it a fully isolated quota — but Klaviyo is phasing out private key auth for partner apps anyway, so plan that migration now.

The Bulk Import Profiles endpoint is rate-limited at 10/s burst and 150/m steady — significantly tighter than the Bulk Subscribe endpoint — and Klaviyo enforces a hard 5 MB payload cap per request. A sync job that batches aggressively and doesn't implement backoff will start receiving 429s, and on platforms like Zapier there is no built-in retry logic that maps cleanly to Klaviyo's 17-retry exponential backoff window. We've also seen a documented case where bulk subscribing via Zapier's Python step adds profiles to a list correctly but never generates a 'Subscribed to List' activity event — meaning any flow triggered by that event will never fire, with no error surfaced anywhere in the workflow.

The /api/campaign-values-reports/ endpoint has a standalone daily rate limit of 225 calls — not a per-minute or per-second limit, but a hard daily ceiling that resets once per day. An automation that polls this endpoint every hour across multiple scenarios in Make or Pipedream, or a dashboard refresh workflow running every few minutes, will burn through that limit in hours and return errors for the rest of the day with no partial data. There is no burst reserve to draw on and no documented way to request a higher daily limit outside of enterprise agreements.