mirrors/n8n-docs
2
0
Fork 0
mirror of https://github.com/n8n-io/n8n-docs.git synced 2025-11-20 17:48:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
e2b2af1aab
n8n-docs/docs/integrations/builtin/credentials/customerio.md

2.8 KiB
Raw Blame History

title description contentType
Customer.io credentials Documentation for Customer.io credentials. Use these credentials to authenticate Customer.io in n8n, a workflow automation platform. integration

Customer.io credentials

You can use these credentials to authenticate the following nodes with Customer.io.

Prerequisites

Create a Customer.io account.

Supported authentication methods

  • API Key

Related resources

Refer to Customer.io's summary API documentation{:target=_blank .external-link} for more information about the service.

For detailed API reference documentation for each API, refer to the Track API documentation{:target=_blank .external-link} and the App API documentation{:target=_blank .external-link}.

Using API key

To configure this credential, you'll need:

  • A Tracking API Key: For use with the Track API{:target=_blank .external-link} at https://track.customer.io/api/v1/. See the FAQs below for more details.
  • Your Region: Customer.io uses different API subdomains depending on the region you select. Options include:
    • Global region: Keeps the default URLs for both APIs; for use in all non-EU countries/regions.
    • EU region: Adjusts the Track API subdomain to track-eu and the App API subdomain to api-eu; only use this if you are in the EU.
  • A Tracking Site ID: Required with your Tracking API Key
  • An App API Key: For use with the App API{:target=_blank .external-link} at https://api.customer.io/v1/api/. See the FAQs below for more details.

Refer to the Customer.io Finding and managing your API credentials documentation{:target=_blank .external-link} for instructions on creating both Tracking API and App API keys.

Why you need a Tracking API Key and an App API Key

Customer.io has two different API endpoints and generates and stores the keys for each slightly differently:

  • The Track API{:target=_blank .external-link} at https://track.customer.io/api/v1/
  • The App API{:target=_blank .external-link} at https://api.customer.io/v1/api/

The Track API requires a Tracking Site ID; the App API doesn't.

Based on the operation you want to perform, n8n uses the correct API key and its corresponding endpoint.