Customer.io setup guide

Agents work with your audiences, campaigns and forms.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Customer.io, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

App API key and Track API credentials

API key.

1. In Customer.io open Account Settings > API Credentials (https://fly.customer.io/settings/api_credentials).
2. Under Track API keys, copy the Site ID and API key of the workspace your agents should use.
3. Under App API keys, create a key for the same workspace, name it "Everdeck", give it a scope that can read data and send messages, and copy it (it is shown only once).
4. Paste all three here. Everdeck detects whether the workspace is in the US or EU region.
5. Optional, for message events: after connecting, open Data & Integrations > Integrations > Reporting Webhooks and paste the webhook signing key shown there.

Field	What to enter
App API key	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.
Track API Site ID	Text. Where to find it.
Track API key	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.
Reporting webhook signing key (only for message events) (optional)	A secret: Everdeck saves it encrypted and never shows it again.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Customer.io until you delete or rotate it there.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• Find people by emailTier 0 · ReadReads outside contentcustomer_io_find_people_by_email

  Find the people in the workspace with this email address. Returns each person's id and cio_id, which the other person actions take.

• Read a personTier 0 · ReadReads outside contentcustomer_io_get_person

  Read a person's attributes, identifiers, devices and whether they are unsubscribed from all messages.

• List messages sent to a personTier 0 · ReadReads outside contentcustomer_io_list_person_messages

  List the messages delivered to a person (last 6 months by default), newest first, with subject, channel, delivery metrics and any failure reason. Use it when a customer says they did not get an email.

• Create or update a personTier 2 · ReversibleReads outside contentcustomer_io_identify_person

  Add a person or update their attributes (for example plan, company or signup date). Only the attributes sent change. Segments and automations that depend on these attributes react to the change. Cannot change unsubscribe status.

• Record an eventTier 3 · ExternalReads outside contentcustomer_io_track_event

  Record that a person did something (for example "demo_requested" with details). Event- triggered automations start immediately and may message the person.

• List segmentsTier 0 · ReadReads outside contentcustomer_io_list_segments

  List segments (data-driven and manual) with their ids, for targeting newsletters.

• Send a transactional emailTier 3 · Externalcustomer_io_send_transactional_email

  Send one person a transactional email from a transactional message template (by id or trigger name) with data for its Liquid placeholders, or with your own subject and HTML.

• List newslettersTier 0 · ReadReads outside contentcustomer_io_list_newsletters

  List one-time sends (newsletters), newest first, with their send state, schedule, target segments and sent time.

• Draft a newsletterTier 2 · ReversibleReads outside contentcustomer_io_create_newsletter_draft

  Create a draft one-time email for one or more segments, with subject and HTML. The audience and name cannot be changed later (delete and recreate instead). Nothing is sent until send_newsletter or schedule_newsletter.

• Send a newsletter nowTier 3 · Externalcustomer_io_send_newsletter

  Send a draft newsletter to its audience immediately. Cannot be undone.

• Schedule a newsletterTier 3 · ExternalReads outside contentcustomer_io_schedule_newsletter

  Schedule a draft newsletter for a future time, or change its scheduled time.

• Read newsletter resultsTier 0 · ReadReads outside contentcustomer_io_get_newsletter_metrics

  Daily (or weekly or monthly) counts for a newsletter: sent, delivered, opened, clicked, converted, bounced, spam reports and unsubscribes. Each metric is a list with one number per period, oldest first; add them up for totals.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Customer.io later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit.

To stop agents using Customer.io, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.