n8n-nodes-klaviyo-api

An n8n community node for Klaviyo — the email and SMS
marketing platform used by a large share of ecommerce stores.

It covers the parts of Klaviyo that automations actually reach for: adding and
updating people, moving them in and out of lists, recording consent, tracking the
events that start flows, and reading back segments, metrics and campaigns. A
trigger node is included so a workflow can start the moment something happens in
Klaviyo.

n8n is a fair-code licensed
workflow automation platform.

• Installation
• Credentials
• Operations
• Trigger
• Example workflows
• Notes and limitations
• Compatibility
• Resources

Installation

Follow the
community node installation guide
and use the package name:

n8n-nodes-klaviyo-api

On self-hosted n8n you can also install it from the command line:

npm install n8n-nodes-klaviyo-api

Credentials

The node authenticates with a private API key.

1. In Klaviyo, go to Settings → Account → API keys.
2. Click Create private API key.
3. Give it a label, and grant read and write access to the scopes you plan to use
   (Profiles, Lists, Segments, Events, Metrics, Campaigns, Webhooks).
4. Copy the key — it starts with pk_ — into the credential in n8n.

Private API keys are account-wide, so scope them down to what the workflow needs
rather than granting full access.

Use the Test button on the credential to confirm it works before building
anything on top of it.

Operations

Profile

Custom properties can be set on create, upsert and update without leaving the UI.

Create or Update is usually the one you want. Create fails on a duplicate,
which in practice means the second time the same customer appears.

List

Create · Get · Get Many · Update · Delete · Get Profiles · Add Profiles ·
Remove Profiles

Adding a profile to a list is not the same as subscribing it. Use Add Profiles
to put someone on a list, and Profile → Subscribe when you have consent to
market to them.

Event

Klaviyo creates the metric the first time it sees a new metric name, so there is
no separate step to define one. Set Unique ID if the workflow might retry:
Klaviyo records an event with a repeated unique ID only once.

Segment

Get · Get Many · Update · Get Profiles

Metric

Get · Get Many

Campaign

Get · Get Many · Delete · Send

Listing campaigns requires choosing a channel — that is Klaviyo's rule, not a
choice made here — and can be narrowed further by status.

Trigger

The Klaviyo Trigger node registers a webhook in your Klaviyo account when the
workflow is activated, and removes it again when the workflow is deactivated. Pick
the topics you want from the dropdown, which is loaded live from your account so
it always matches what Klaviyo currently offers.

Every delivery is signed by Klaviyo, and the trigger rejects any request whose
signature does not match, so the webhook URL alone is not enough for someone else
to push data into your workflow. You can supply your own secret key under
Options, or leave it empty and one is derived for you.

Klaviyo only delivers to https URLs. A local n8n on plain http cannot receive
these webhooks; the node says so when you activate the workflow rather than
failing silently later.

Example workflows

Sync new customers into a list

Shopify Trigger → Klaviyo: Profile → Create or Update →
Klaviyo: List → Add Profiles

Track a custom event that starts a flow

Webhook → Klaviyo: Event → Create with metric name Trial Started and a
plan property. Build the Klaviyo flow off that metric.

Send a Slack alert when someone unsubscribes

Klaviyo Trigger on the unsubscribe topic → Slack: Send Message

Weekly reporting

Schedule Trigger → Klaviyo: Segment → Get Profiles → Google Sheets: Append

Notes and limitations

• API revision. Klaviyo versions its API by date and this node pins revision
  2026-07-15. Klaviyo supports each revision for two years, so a pinned revision
  keeps existing workflows working when Klaviyo ships breaking changes. Newer
  fields become available when the node is updated.
• Consent and events are queued jobs. Subscribe, Unsubscribe and Create Event
  return 202 Accepted immediately and Klaviyo applies them afterwards. The node
  emits a confirmation item so the branch keeps running, but reading the profile
  back in the same execution may still show the old state. A 202 means accepted,
  not applied - if a queued change never shows up, check the account itself rather
  than the workflow, since the API answers 202 either way.
• Campaign creation is not included. Building a campaign needs audiences, a
  send strategy and message content, which is a large form for something almost
  everyone does in Klaviyo's editor. Campaigns can be listed, read, sent and
  deleted here.
• Limit is capped per resource. Klaviyo allows a different maximum page size on
  every collection and rejects anything larger outright rather than clamping: 100
  for profiles and campaigns, but only 10 for lists and segments, and
  /api/metrics takes no page size at all. The Limit field carries the real
  maximum for the resource you picked. To go past it, switch on Return All,
  which pages through with a cursor.
• Rate limits. Klaviyo applies per-endpoint burst and steady limits and answers
  429 when you cross them. A Get Many node runs once per incoming item, so a
  chain of them multiplies requests quickly - set Execute Once on read nodes
  that only need to run a single time. Use Retry On Fail for bulk work.
• Profile IDs, not emails. List Add/Remove Profiles takes Klaviyo profile IDs.
  Look the profile up first (Profile → Get Many, filtered by email) if you only
  have an address.

Compatibility

Tested against n8n 2.x. Requires Node.js 20.15 or newer, which n8n itself already
requires.

The package has no runtime dependencies.

Resources

• n8n community nodes documentation
• Klaviyo API reference
• Klaviyo API versioning policy

License

MIT