Actions17
Overview
This node interacts with the Klaviyo API to retrieve detailed information about a specific event by its unique identifier. It is designed to fetch one event at a time, allowing users to specify which fields of the event they want to retrieve, as well as optionally include related resources such as associated metrics or profiles.
Common scenarios where this node is beneficial include:
- Fetching detailed data about a particular user event for analysis or reporting.
- Enriching workflows with event-specific information, such as timestamps or custom properties.
- Combining event data with related profile or metric information to create comprehensive customer insights.
For example, a marketing automation workflow might use this node to get details of a purchase event, including the event timestamp and associated customer profile data, to trigger personalized follow-up campaigns.
Properties
| Name | Meaning |
|---|---|
| Event ID | The unique identifier of the event to retrieve. This is required to specify which event to fetch. |
| Event Fields | Select which fields of the event to return. Options: datetime, event_properties, timestamp, uuid. |
| Additional Resources | Optionally include related resources in the response. Choices are metric and/or profile. |
| Metric Fields | If metric is included in Additional Resources, select which metric fields to return. Options: name, created, updated, integration. |
| Profile Fields | If profile is included in Additional Resources, select which profile fields to return. Options include email, phone_number, external_id, first_name, last_name, organization, locale, title, image, created, updated, last_event_date, various location fields (e.g., location.city, location.country), and properties. |
Output
The node outputs JSON data representing the requested event and any included related resources:
- The main output contains the event object with the selected event fields.
- If additional resources (
metricand/orprofile) are requested, their respective objects with the selected fields are included in the output. - The structure follows the Klaviyo API's JSON:API format, typically including nested objects for related resources.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Klaviyo API.
- The node uses the base URL
https://a.klaviyo.com/apiand expects JSON:API formatted requests and responses. - Proper configuration of the API key credential within n8n is necessary for successful operation.
Troubleshooting
- Missing or invalid Event ID: The node requires a valid event ID; ensure it is provided and correctly formatted.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Empty or incomplete response: Check that the requested fields and included resources exist for the specified event.
- Network or rate limiting issues: The Klaviyo API may enforce rate limits; handle retries or backoff accordingly.
- Incorrect field selections: Selecting fields not available for the resource or without including the related resource (e.g., selecting metric fields without including metric) will result in missing data.