List Profiles: 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
Page Size page_size	string	Optional	Number of profiles to return per page (default: 20, max: 100)

Sample request

{
  "page_size": "20"
}

Returns

{
  "data": [
    {
      "id": "01JABCDEF123456789",
      "type": "profile",
      "attributes": {
        "email": "customer@example.com",
        "created": "2026-01-15T12:00:00+00:00",
        "updated": "2026-04-20T09:30:00+00:00",
        "last_name": "Doe",
        "first_name": "John",
        "phone_number": "+15551234567"
      }
    }
  ],
  "links": {
    "next": null,
    "self": "https://a.klaviyo.com/api/profiles"
  }
}

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

FAQ

Questions about List Profiles.

What does the List Profiles action do in Klaviyo?

Lists profiles (contacts) from your Klaviyo account with their email, phone, and properties. Used for exports or for syncing into your CDP.

What inputs does List Profiles require?

List Profiles has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Profiles support batch operations?

Yes. Run List Profiles 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