Integrations / Customer.io

Customer.io

Customer.io lifecycle messaging and growth automation for people, events, campaigns, newsletters, broadcasts, and journeys.

API key

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A Customer.io workspace you can administer.

Workspace admin who can open Settings → API credentials.

Vendor setup

Get the credential

Open API credentials

In Customer.io, go to Settings → Account Settings → API Credentials (App API Keys).

Create an App API key

Click Create App API Key. Name it for Telara. Copy it. This is not a Track API key and not a CDP key.

Paste in Telara

Settings → Integrations → Customer.io. Paste the App API key. For EU workspaces, also enter the EU regional host Telara asks for.

In Telara

Connect in Telara

API key

Customer.io App API key for workspace and messaging APIs. Store region_base_url for EU workspaces when needed.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

App Api Key

Knowledge

What gets indexed

Resource	Coverage
Campaign	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Campaign	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Campaign.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Track API keys ingest events; they cannot read workspace objects. Use the App API key.

US vs EU workspaces are different hosts. Using the US host on an EU workspace fails Connect.