Nexra
All connectors
Implemented
Marketing & advertising
Customer.io logo

Customer.io

Search people and read profiles, segments, automations, broadcasts, one-time sends, messages and activity in Customer.io; create manual segments and send transactional messages.

Feed Customer.io engagement and delivery data into CRMs and warehouses, and trigger transactional email, SMS and push from operational flows.

Build a flow with Customer.ioProvider API documentation

Source actions

26

Destination actions

4

Data types

23

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

activities
  • List activities
    Source

    Workspace activity log (events, attribute changes, deliveries, page views).

    activities.list
broadcast metrics
  • Get broadcast metrics
    Source

    Delivery metric series for a broadcast.

    broadcast_metrics.get
broadcasts
  • Get broadcast
    Source

    An API-triggered broadcast.

    broadcasts.get
  • List API-triggered broadcasts
    Source

    API-triggered broadcasts with state and actions (read-only).

    broadcasts.list
campaign actions
  • List automation actions
    Source

    Messages and other actions in an automation (10 per page).

    campaign_actions.list
campaign metrics
  • Get automation metrics
    Source

    Delivery metric series for an automation over an explicit window (version 2).

    campaign_metrics.get
campaigns
  • Get automation
    Source

    An automation with trigger, state and actions.

    campaigns.get
  • List automations
    Source

    Automations (campaigns) with trigger type, state and actions.

    campaigns.list
customer activities
  • List a person's activities
    Source

    Activity log entries (events, attribute changes, deliveries) for a person.

    customer_activities.list
customer messages
  • List a person's messages
    Source
    Incremental

    Deliveries sent to a person with per-delivery metric timestamps.

    customer_messages.list
customer profiles
  • Get people in bulk
    Source

    Attributes and devices for up to 100 people by identifier.

    customer_profiles.list
customer segments
  • List a person's segments
    Source

    Segments the person currently belongs to.

    customer_segments.list
customers by email
  • Find people by email
    Source

    People whose email address matches exactly.

    customers_by_email.list
customers
  • Get person
    Source

    A person's attributes, attribute timestamps, unsubscribe flag and devices.

    customers.get
  • Search people
    Source

    Find people by segment membership and attribute conditions (all conditions must match).

    customers.search
messages
  • Get message
    Source

    A single delivery with metrics.

    messages.get
  • List messages
    Source
    Incremental

    Deliveries across the workspace with per-delivery metric timestamps.

    messages.list
newsletter metrics
  • Get one-time send metrics
    Source

    Delivery metric series for a one-time send.

    newsletter_metrics.get
newsletters
  • Get one-time send
    Source

    A one-time send (newsletter).

    newsletters.get
  • List one-time sends
    Source

    One-time sends (newsletters) with send state and schedule.

    newsletters.list
segment counts
  • Get segment size
    Source

    Number of people currently in a segment.

    segment_counts.get
segment members
  • List segment members
    Source

    People in a segment.

    segment_members.list
segments
  • Create manual segment
    Destination
    Not retried automatically
    Approval before production

    Creates an empty manual segment.

    segments.create
  • Get segment
    Source

    A segment with its conditions and build state.

    segments.get
  • List segments
    Source

    Dynamic and manual segments (archived segments are excluded).

    segments.list
subscription preferences
  • Get subscription preferences
    Source

    A person's subscription topics with subscribed state and the global unsubscribe flag (read-only).

    subscription_preferences.get
transactional emails
  • Send transactional email
    Destination
    Not retried automatically
    Approval before production

    Sends a transactional email template to one person.

    transactional_emails.send
transactional messages
  • List transactional messages
    Source

    Transactional message templates you can send with the send operations.

    transactional_messages.list
transactional push
  • Send transactional push
    Destination
    Not retried automatically
    Approval before production

    Sends a transactional push template to a person's devices.

    transactional_push.send
transactional sms
  • Send transactional SMS
    Destination
    Not retried automatically
    Approval before production

    Sends a transactional SMS template to one person.

    transactional_sms.send

Authentication

App API key (bearer)

Plans and access

All Customer.io Journeys plans include the App API. App API keys are workspace-scoped and can be limited to specific scopes; transactional sends require a transactional message in the workspace.

Test environment

A trial workspace (or a separate test workspace) works for testing.

Rate limits

App API: 10 requests per second; transactional sends 3,000 requests per 3 seconds (soft limit). HTTP 429 when exceeded.

Pagination

Cursor lists return `next`; Nexra passes it back as `start`. Automation, broadcast and segment lists return everything in one response.

Provider events

Reporting webhooks for message and delivery events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • The Track API (track.customer.io, Basic auth with site ID and API key) is a different host and credential, so identifying people, tracking events and changing subscription preferences are not available on this connection.
  • API-triggered broadcasts and one-time sends to audiences are not implemented; only person-addressed transactional messages can be sent.
  • Deleting people, segments or messages is not implemented.
  • Transactional sends have no idempotency key; uncertain sends are not repeated automatically.
  • sendToUnsubscribed is only sent when a flow sets it explicitly, so the template's consent setting applies by default.
  • Activities are guaranteed for the past 30 days; message lists default to the last 6 months.

Developer reference

  1. Create the Customer.io credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Customer.io, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Customer.io docsAPI referenceCustomer.io docsAuthenticationCustomer.io docsRate limitsCustomer.io docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/customer-io and the Connections API.