Skip to content

Automate Customer.io

Follow what your Customer.io messages do after they go out. Bounces and spam complaints reach your team as they happen, unsubscribes come with the message that caused them, and campaign numbers arrive as a weekly table. Describe what you want to your AI assistant, check what it will do, and it keeps running with your laptop closed.

Try asking

Create a ClickRuntime automation: whenever a Customer.io email bounces or is marked as spam, post the person's email, the message name and the event type to #deliverability in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Build your own

Build any Customer.io automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Customer.io should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every day, find Customer.io people who signed up a week ago but never triggered an activation event and send me the list.

When a Stripe subscription is created, update the person's plan attribute in Customer.io.

When a user cancels in Stripe, send a Customer.io event, have AI summarize their support history from Intercom and post it in Slack.

Beyond chat

Have Customer.io work when you're not in the chat

Connecting Customer.io to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Customer.io

Customer.io has two APIs with their own credentials, both created in your workspace. Reports use an App API key. Event alerts use a reporting webhook you add in Customer.io, with its signing key so each event can be checked as genuine.

Customer.io

Messaging automation

  1. In Customer.io, go to Account Settings, then API Credentials.
  2. Create an App API key and give it only the access the automation needs. Read access is enough for reports.
  3. If an automation sends data to Customer.io, also copy your Site ID and Track API key from the same page.
  4. Note whether your account is in the US or EU region.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the keys as secrets for Customer.io.

Good to know

Customer.io limits that affect automations

  • Customer.io accounts are hosted in the US or the EU, and each uses its own API addresses, so tell your assistant which region you're in.
  • The App API allows about 10 requests per second, which is plenty for reports on a normal number of campaigns.
  • Reporting webhooks must get an answer within 4 seconds. Alerts are received right away and the slower work happens afterwards.
  • Broadcasts can be triggered at most once every 10 seconds.

FAQ

Questions about automating Customer.io

What can ClickRuntime see in my Customer.io workspace?
For reports, whatever your App API key allows, such as campaigns and their metrics. Alerts don't need a key at all: Customer.io sends the events to the automation's link, and the signing key is used to check they came from your workspace.
How do bounce and unsubscribe alerts work?
You add the automation's link as a reporting webhook in Customer.io and choose the events, such as bounced, spammed or unsubscribed. Each event is checked against the `X-CIO-Signature` header and then passed on.
Does it matter whether my account is in the EU?
Yes. EU workspaces use separate API addresses. Calls to the US addresses get redirected through the US, so the automation uses the EU ones when you say your workspace is there.
Which numbers are in the weekly digest?
Sent, opened and clicked counts per campaign for the last seven days, laid out as a table.
Do I need AI for Customer.io automations?
No. These run without it. If you want a written summary or a short comment on the numbers, that uses the AI that comes with every ClickRuntime plan, so you don't need your own AI key.
Is this a Customer.io connector for ChatGPT or Claude?
Not for chatting with Customer.io data. A chat connector lets your assistant read and change Customer.io while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Customer.io event.

Tell your assistant what Customer.io should do

Free plan. No credit card.