Klaviyo icon

Klaviyo

Interact with the Klaviyo API

Actions17

Profile → Get Many

AI-generated

Overview

This node interacts with the Klaviyo API to retrieve multiple profile records. It supports pagination through a page cursor and page size, sorting by various profile fields, and filtering based on specific profile attributes or date fields. Users can also specify which profile fields to return in the response. This node is useful for scenarios where you need to fetch and process batches of user profile data from Klaviyo, such as for marketing analysis, customer segmentation, or data synchronization.

Use Case Examples

  1. Fetch the first 20 profiles sorted by creation date in descending order.
  2. Retrieve profiles filtered by email or phone number with specific fields like email, first name, and last name.
  3. Paginate through profiles using the page cursor to process large datasets in batches.

Properties

Name Meaning
Page Cursor Cursor for pagination to fetch the next set of profiles.
Page Size Number of profiles to retrieve per request, with a maximum of 100.
Sort Field and order to sort the profiles by, such as id, email, created, or updated, in ascending or descending order.
Filters Filters to narrow down profiles based on field values or date conditions, supporting operators like equals, any (for multiple values), greater-than, and less-than.
Query Parameters Specify which profile fields to include in the response, such as email, phone number, external ID, name, location details, and custom properties.
Request Options Advanced request settings including batching, SSL certificate validation, proxy configuration, and request timeout.

Output

JSON

  • profiles - Array of profile objects retrieved from Klaviyo, each containing the requested fields and attributes.

Dependencies

  • Klaviyo API key credential

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to access profile data.
  • Check that the page size does not exceed the maximum allowed (100) to avoid request errors.
  • Verify filter syntax and values to prevent malformed query parameters causing API errors.
  • If using a proxy or ignoring SSL issues, confirm network settings are correct to avoid connection failures.

Links

Discussion