Actions17
Overview
This node integrates with the Klaviyo API to create a new user profile. It is designed to add or update profile information such as email, phone number, external ID, and various personal or location attributes. This functionality is useful for marketing automation, customer segmentation, and personalized communication workflows where maintaining up-to-date user profiles is essential.
Practical examples include:
- Adding a new customer profile when they sign up on a website.
- Updating existing profile details like phone number or address after a user edits their account.
- Creating profiles based on external identifiers from other systems to unify customer data.
Properties
| Name | Meaning |
|---|---|
| One or more of the following are required: email, phone number, or external ID | A notice indicating that at least one of these identifiers must be provided to create or update a profile. |
| Attributes | A collection of key-value pairs representing profile attributes. Keys can be selected from predefined options such as email, phone number, external ID, first name, last name, organization, locale, title, image, created date, updated date, last event date, and various location fields (address1, address2, city, country, latitude, longitude, region, zip, timezone, IP). Values are strings entered by the user. |
| Properties | Additional custom key-value string pairs for profile properties not covered by the predefined attribute keys. |
Output
The node outputs JSON data representing the created or updated profile in Klaviyo. The output includes the profile's attributes and properties as sent in the request, confirming the successful creation or update.
If binary data were involved (not indicated here), it would typically represent files or images related to the profile, but this node focuses solely on JSON profile data.
Dependencies
- Requires an API key credential for authenticating with the Klaviyo API.
- The node sends requests to
https://a.klaviyo.com/apiwith appropriate headers for JSON API content type. - No additional external dependencies beyond the Klaviyo API and its authentication.
Troubleshooting
- Missing Required Identifiers: If none of email, phone number, or external ID is provided, the API will likely reject the request. Ensure at least one identifier is included.
- Invalid Attribute Keys: Using keys outside the predefined list or malformed keys may cause errors. Use only supported attribute keys or add them under "Properties" as custom key-value pairs.
- Authentication Errors: Invalid or missing API credentials will result in authorization failures. Verify the API key is correctly configured in n8n credentials.
- API Rate Limits: Excessive requests might trigger rate limiting by Klaviyo. Implement retry logic or reduce request frequency if needed.