Actions17
Overview
This node interacts with the Klaviyo API to retrieve detailed information about a specific user profile. The "Get One" operation under the "Profile" resource fetches data for a single profile identified by its unique ID. This is useful in scenarios where you want to access or analyze individual customer details, such as their contact information, location, and custom properties.
Practical examples include:
- Fetching a user's email and phone number before sending a personalized marketing message.
- Retrieving profile metadata like last event date or organization to segment users dynamically.
- Accessing location details for geo-targeted campaigns.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the profile to retrieve. |
| Query Parameters | Optional parameters to specify which profile fields to return. Available fields include: |
| - email, phone_number, external_id, first_name, last_name, organization, locale, title, image | |
| - created, updated, last_event_date | |
| - location and its subfields: address1, address2, city, country, latitude, longitude, region, zip, timezone, ip | |
| - properties (custom profile properties) |
The "Query Parameters" property allows selecting multiple fields to limit the response to only those attributes, optimizing data usage.
Output
The node outputs JSON data representing the requested profile's details. The structure corresponds to the selected fields and includes standard profile attributes such as contact info, timestamps, location data, and any custom properties.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Klaviyo API.
- The node makes HTTP requests to
https://a.klaviyo.com/api. - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing profile ID will result in errors or empty responses.
- Insufficient permissions or invalid API key can cause authentication failures.
- Requesting fields not available or misspelled may lead to incomplete data or errors.
Error messages:
- 404 Not Found: The specified profile ID does not exist. Verify the ID.
- 401 Unauthorized: Authentication failed. Check the API key credential.
- 400 Bad Request: Invalid query parameters. Ensure field names are correct.
Resolving these typically involves verifying input values, ensuring valid credentials, and confirming API access rights.