Klaviyo icon

Klaviyo

Interact with the Klaviyo API

Actions17

Metric → Get Many

AI-generated

Overview

This node interacts with the Klaviyo API to retrieve multiple Metric records. It supports pagination through a page cursor, filtering based on integration category or name, and selecting specific fields to return for both metrics and related flow triggers. It is useful for scenarios where you need to fetch a list of metrics with optional filtering and field selection, such as analyzing performance metrics or integrating metric data into workflows.

Use Case Examples

  1. Fetch all metrics with specific fields like name and created date.
  2. Retrieve metrics filtered by integration name or category.
  3. Include additional related resources like flow triggers and specify which flow fields to return.

Properties

Name Meaning
Page Cursor Used for pagination to specify the cursor for the page of results to retrieve.
Filters Allows filtering metrics by integration category or name with specific values.
Metric Fields Select which fields of the metric resource to include in the response, such as name, created, updated, and integration.
Additional Resources Specify additional related resources to include in the response, such as flow triggers.
Flow Fields Select which fields of the flow trigger resource to include, requires 'flow-triggers' to be included in Additional Resources.
Request Options Settings for request behavior including batching, SSL certificate validation, proxy configuration, and timeout.

Output

JSON

  • metrics - Array of metric objects retrieved from the Klaviyo API.
  • pagination - Pagination information including cursors for navigating through pages of results.

Dependencies

  • Klaviyo API with an API key credential

Troubleshooting

  • Ensure the API key credential is correctly configured and has permissions to access metric data.
  • Check that the page cursor value is valid for pagination to avoid empty or repeated results.
  • Verify filter values match existing integration categories or names to get expected results.
  • If including additional resources like flow triggers, ensure the related fields are correctly specified to avoid incomplete data.

Discussion