Piano Analytics icon

Piano Analytics

Use the Piano Analytics API
Join our community

Actions6

Overview

This node integrates with the Piano Analytics API, specifically supporting multiple resources including the Enrichment API. For the Enrichment API - Post Data operation, it allows users to enrich their data by sending custom enrichment payloads to Piano Analytics.

Typical use cases include:

  • Sending additional contextual or enriched data related to your analytics events.
  • Reconciling external data sources with Piano Analytics datasets using a reconciliation key.
  • Automating data enrichment workflows within n8n to enhance analytics insights.

For example, you might post customer profile updates or transaction details that complement event tracking data, enabling more detailed analysis downstream.

Properties

Name Meaning
Organization Code The unique code identifying your organization in Piano Analytics.
Enrichment ID Identifier for the specific enrichment dataset or process you want to target.
Reconciliation Key A key used to reconcile or match incoming enrichment data with existing records.
Enrichment Data JSON object containing the actual enrichment data payload to be sent to the API.

Output

The node outputs an array of JSON objects representing the response from the Piano Analytics Enrichment API after posting the data. Typically, this will be the parsed JSON response returned by the API confirming success or providing any relevant metadata.

If no content is returned (HTTP 204), the output will contain an object indicating "204 No Content" status.

Dependencies

  • Requires an API key credential for authenticating with the Piano Analytics API.
  • The node uses the x-api-key header constructed from the access and secret keys combined.
  • Network access to https://import.atinternet.io/ endpoint is required.
  • No other external dependencies are needed.

Troubleshooting

  • Missing Required Fields: The node throws errors if Organization Code, Enrichment ID, or Reconciliation Key are not provided. Ensure these are correctly set.
  • Invalid JSON in Enrichment Data: The enrichmentData property must be valid JSON. Invalid JSON will cause parsing errors.
  • Authentication Errors: If the API key credentials are missing or invalid, the node will fail to authenticate.
  • API Endpoint Issues: Ensure network connectivity to the Piano Analytics import endpoint and that the URL format matches the expected pattern.
  • Error Messages: Errors from the API or internal exceptions are wrapped and reported with messages prefixed by "Error calling Piano Analytics API:" followed by the original error message.

Links and References

Discussion