Klaviyo icon

Klaviyo

Interact with the Klaviyo API

Actions17

Metric → Get One

AI-generated

Overview

This node interacts with the Klaviyo API to retrieve detailed information about a specific Metric by its ID. It is useful for scenarios where you need to fetch and analyze data related to a particular metric, such as tracking user behavior or campaign performance in Klaviyo. For example, you can use this node to get the name, creation date, update date, and integration details of a metric, along with optionally including related flow triggers and their fields.

Use Case Examples

  1. Retrieve a metric by its ID to display its details in a dashboard.
  2. Fetch a metric along with associated flow triggers to analyze campaign automation.

Properties

Name Meaning
Metric ID The unique identifier of the metric to retrieve, required for the operation.
Metric Fields Select specific fields of the metric to include in the response, such as name, created, updated, and integration.
Additional Resources Optionally include related resources such as flow triggers associated with the metric.
Flow Fields Specify which fields of the flow triggers to include if flow triggers are requested, such as name, status, archived, created, updated, and trigger type.
Request Options Advanced settings for the HTTP request such as batching, SSL certificate validation, proxy configuration, and timeout settings.

Output

JSON

  • id - The unique identifier of the retrieved metric.
  • name - The name of the metric.
  • created - The creation timestamp of the metric.
  • updated - The last update timestamp of the metric.
  • integration - Details about the integration associated with the metric.
  • flowTriggers - Optional included flow triggers related to the metric, if requested.

Dependencies

  • Klaviyo API key credential

Troubleshooting

  • Ensure the Metric ID is correctly provided and exists in Klaviyo to avoid 'not found' errors.
  • Verify API credentials are valid and have necessary permissions to access metric data.
  • If including additional resources like flow triggers, ensure the related data exists and the fields are correctly specified.
  • Check network settings such as proxy and SSL options if requests fail due to connectivity or security issues.

Links

Discussion