BusyBot

Reference · Credentials

Customer.io API credentials

Used by 2 BusyBot nodes.

Type customerIoApi 4 fields

The Customer.io credential carries two different API keys because Customer.io has two APIs: a Tracking API key with site ID for writing customers and events, and an App API key for campaign data — which the trigger requires. The region setting decides which hostname requests go to.

Fields

FieldTypeRequiredNotes
Tracking API Key
trackingApiKey		 password Yes API key for the Customer.io Tracking API
Region
region		 string Yes Customer.io region.
Tracking Site ID
trackingSiteId		 string No Site ID for the Customer.io Tracking API
App API Key
appApiKey		 password Yes API key for the Customer.io App/Beta API (required for customerio_trigger lifecycle)

Getting your credentials

  1. Sign in to Customer.io and open the account settings covering API credentials.
  2. From the Tracking API section, copy the site ID and the tracking API key. These write customers and events.
  3. From the App API section, create and copy an App API key. This reads campaigns and metrics, and the Customer.io trigger requires it.
  4. Set Region to match your workspace — Global or EU. This determines the tracking hostname requests are sent to.

Permissions and scopes

App API keys can usually be scoped when created. Grant only what the workflow reads or writes.

The region is not cosmetic: an EU workspace addressed with the Global hostname will fail, and vice versa.

Troubleshooting

  • Tracking works but campaign operations fail — the App API key is missing. The two APIs use different keys.
  • 404 or connection failures — the region does not match your workspace.
  • Events not appearing — check the site ID belongs to the same workspace as the tracking key.

Frequently asked questions

Why are there two API keys?

Customer.io has two APIs. The Tracking API writes customers and events; the App API reads campaigns and metrics. The trigger requires the App API key specifically.

What does the region setting do?

It selects the tracking hostname — Global or EU. An EU workspace addressed with the Global host fails, so it must match where your workspace lives.

Do I need the site ID?

For the Tracking API, yes — it pairs with the tracking key to identify the workspace.

Nodes that use Customer.io API

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.