Actions17
Event → Get One
AI-generatedOverview
This node interacts with the Klaviyo API to retrieve detailed information about a single event by its Event ID. It is useful for scenarios where you need to fetch specific event data for analysis, reporting, or integration with other systems. For example, you might use it to get the details of a user's purchase event or a custom event triggered in your marketing automation.
Use Case Examples
- Retrieve a specific event by its ID to analyze user behavior.
- Fetch event details including associated metrics and profile information for personalized marketing.
Properties
| Name | Meaning |
|---|---|
| Event ID | The unique identifier of the event to retrieve. This is a required field for the 'Get One' operation on the Event resource. |
| Event Fields | Specifies which fields of the event to include in the response, such as datetime, event_properties, timestamp, and uuid. This allows for selective data retrieval to optimize performance and relevance. |
| Additional Resources | Additional related resources to include in the response, such as metric and profile data associated with the event. |
| Metric Fields | Specifies which fields of the metric resource to include if 'metric' is selected in Additional Resources. Fields include name, created, updated, and integration. |
| Profile Fields | Specifies which fields of the profile resource to include if 'profile' is selected in Additional Resources. This includes contact details, location, and other profile-specific information. |
| Request Options | Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout duration. |
Output
JSON
id- The unique identifier of the retrieved event.type- The type of the event resource.attributesdatetime- The datetime when the event occurred.event_properties- Properties associated with the event.timestamp- Timestamp of the event.uuid- UUID of the event.
includedmetric- Included metric resource data if requested.profile- Included profile resource data if requested.
Dependencies
- Klaviyo API key credential
Troubleshooting
- Ensure the Event ID is correctly provided and exists in the Klaviyo system to avoid 'not found' errors.
- Verify that the API key credential is valid and has the necessary permissions to access event data.
- If additional resources like metric or profile are requested, ensure the corresponding fields are correctly specified to avoid incomplete data.
- Check network settings such as proxy and SSL options if requests fail due to connectivity issues.
- Timeout settings should be adjusted based on network speed and server response times to prevent premature request termination.
Links
- Klaviyo Events API Documentation - Official documentation for Klaviyo's Events API, detailing endpoints, parameters, and usage examples.