ActionKlaviyoUpdated September 2026

How do I subscribe a Klaviyo profile to a list?

Short answer: You can subscribe profile in Klaviyo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Klaviyo Subscribe Profile action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Subscribe Profile in Klaviyo — start free All 5 Klaviyo actions

Subscribe Profile in Klaviyo — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
List ID list_id	string	Required	The ID of the Klaviyo list to subscribe to
Email email	string	Required	Email address to subscribe

Sample request

{
  "list_id": "e.g. UxYzAb",
  "email": "customer@example.com"
}

Returns

{
  "data": {
    "id": "01JSUBSCR123456789",
    "type": "profile-subscription-bulk-create-job",
    "attributes": {
      "status": "queued",
      "created_at": "2026-04-23T10:00:00+00:00",
      "total_count": 1,
      "completed_count": 0
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Subscribe Profile.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Klaviyo

2 Google Sheets triggers

HubSpot → Klaviyo

18 HubSpot triggers

FAQ

Questions about Subscribe Profile.

What does the Subscribe Profile action do in Klaviyo?

Subscribes a profile to a Klaviyo list with explicit email/SMS consent (single or double opt-in based on the list config). Use after a signup form fills.

What inputs does Subscribe Profile require?

Required: List ID, Email. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Klaviyo returns an error?

The run history shows the failed step with its input and the error message Klaviyo returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Subscribe Profile support batch operations?

Run Subscribe Profile inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Klaviyo's rate limits.

More actions