Subscribe Profile: Klaviyo action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Subscribe Profile support batch operations?

Yes. Run Subscribe Profile inside a Loop node to process arrays. Tiny Command handles Klaviyo's rate limits automatically so you don't have to throttle manually.

More actions