# Klaviyo AI automation and integrations > Klaviyo is built for ecommerce email and SMS and already includes predictive analytics and AI content tools, so use those before building. Custom automation helps with data Klaviyo does not have, such as offline sales, support tickets or B2B accounts, and with content and reporting workflows. The API uses scoped private keys and a dated revision header. Zapier and Make have Klaviyo apps; n8n connects through the HTTP Request node. - Category: Marketing - Vendor: https://www.klaviyo.com/ - How to connect: Klaviyo REST API; System webhooks; Flow webhook actions; Zapier and Make apps; n8n HTTP Request node - Authentication: Private API key with scopes (read-only, full or custom) sent in the Authorization header, or OAuth 2.0 for apps used by other accounts - Notes: Every request needs a revision header naming the API version date. Rate limits are per account with burst and steady windows, and all private-key traffic shares one pool, so spread syncs out. - Last updated: 2026-10-14 ## What you can automate with Klaviyo - **Event sync from systems Klaviyo cannot see.** Send offline purchases, subscription changes, support tickets or app usage to Klaviyo as events so flows can trigger on them. Guide: https://www.lumeor.studio/guides/automate-data-sync-between-apps/ - **Product descriptions and catalog copy.** Generate and refresh product descriptions and email-ready blurbs from catalog data, reviewed before publishing. Guide: https://www.lumeor.studio/guides/ai-ecommerce-product-descriptions/ - **Campaign content from a single brief.** Turn a launch brief into email and SMS variants in your brand voice, saved as drafts for the marketer to finish. Guide: https://www.lumeor.studio/guides/ai-content-repurposing-pipeline/ - **Review requests and replies.** Trigger review requests after delivery and draft replies to new reviews, with negative reviews routed to support. Guide: https://www.lumeor.studio/guides/automate-review-responses/ - **Support context for winback flows.** Hold promotional flows for customers with an open support issue and tag recent complaints so messaging fits. - **Weekly email and SMS performance notes.** Pull campaign and flow metrics and write a short weekly summary with the one test worth running next. ## What makes Klaviyo easy to automate Klaviyo's data model is simple and event-based. Profiles hold properties, and events (metrics) such as "Placed Order" or "Viewed Product" drive flows and segments. If you can send an event with the right profile and properties, Klaviyo can act on it. That is why most Klaviyo automation work is really data plumbing: getting the right events in, cleanly and on time. The API covers profiles, lists, segments, events, catalogs, campaigns, flows, templates and reporting. Shopify and other major ecommerce platforms connect natively, and Zapier and Make both have Klaviyo apps. n8n has no built-in Klaviyo node, so we use HTTP requests, which works well because the API is consistent. ## The AI layer, and Klaviyo's built-in intelligence Klaviyo includes more AI than most email tools: predictive analytics (expected next order date, predicted lifetime value, churn risk), AI-assisted segment building, subject line and content generation, and send-time optimization. Do not rebuild those. A custom churn model fed by the same order data is unlikely to beat what Klaviyo already computes. Custom AI is useful around Klaviyo when: - **Signals live outside the store.** Support complaints, returns from a separate system, wholesale orders or in-store purchases. Sending them as events makes Klaviyo's own targeting smarter. - **Catalog content needs work at scale.** Writing or refreshing hundreds of product descriptions is a good model task with a human review step. See our [product description guide](/guides/ai-ecommerce-product-descriptions/). - **Reviews and replies.** Routing negative reviews to support and drafting public replies, covered in [automating review responses](/guides/automate-review-responses/). ## Limits to plan around - **Revision header.** Pin a revision and schedule upgrades. Some newer endpoints may require a specific revision. - **Key scopes.** Scopes are set when a key is created and cannot be added later. Create a scoped key per integration rather than reusing one full-access key. - **Rate limits.** Limits are per account and per endpoint with burst and steady windows. All private-key traffic shares the pool, so a backfill can slow a live sync. - **Webhook access.** System webhooks are available only to Advanced KDP customers and app partners, and Klaviyo limits concurrent deliveries to each endpoint. Use one webhook with several topics instead of many webhooks. - **Consent.** Email and SMS consent are separate and SMS rules are strict. Never set consent from a sync unless the source captured it properly. - **Profile identity.** Profiles match on email, phone or external ID. Inconsistent identifiers across systems create duplicate profiles. ## How Lumeor typically connects it For Shopify brands we leave the native Shopify integration in place and add an n8n layer for everything else. Typical builds send helpdesk events (ticket opened, complaint category) and subscription or 3PL events into Klaviyo, so flows can pause promotions for unhappy customers or trigger timely replenishment. Content workflows draft product copy and campaign variants from a brief and store them for review. We have built ecommerce AI tooling before, including a [Shopify AI copilot](/case-studies/shopify-ai-copilot). A single sync or content workflow typically sits in our workflow automation band. [Book a call](/start/) to scope yours. ## Frequently asked questions ### Do I need custom AI if Klaviyo already has AI features? Often you do not, at least at first. Klaviyo includes predictive analytics such as expected next order date, predicted lifetime value and churn risk, plus AI tools for writing and segment building. Use those. Custom work pays off when the data Klaviyo needs lives somewhere else, or when content has to be assembled from your own sources. ### Does n8n have a Klaviyo node? No built-in node exists. n8n connects through the HTTP Request node with a private API key and the revision header. Zapier and Make both have Klaviyo apps that cover profiles, lists, events and campaigns for simpler workflows. ### How do I get events out of Klaviyo? Two ways. A flow can include a webhook action that posts to your endpoint when a customer reaches that step, and Klaviyo's system webhooks can forward topics such as email, SMS and consent events. System webhooks are limited to Advanced KDP customers and Klaviyo app partners, so flow webhook actions are the usual route for everyone else. ### What is the revision header? Klaviyo versions its API by date. Each request sends a revision header with the version date you built against, which protects your integration from breaking changes. Plan to update the revision on a schedule, since older revisions are eventually retired. --- Source: https://www.lumeor.studio/tools/klaviyo/ Published by Lumeor Studio, Newtown, PA. hello@lumeor.studio. Get a written scope: https://www.lumeor.studio/start/