Skip to content
customer.io logoConvertKit logo

Connect customer.io to ConvertKit

Move data between customer.io and ConvertKit the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

customer.io triggers
0
customer.io actions
3
ConvertKit triggers
12
ConvertKit actions
35

Automation ideas

What you can build with customer.io and ConvertKit

A few flows teams run between customer.io and ConvertKit. Use one as a starting point, or build your own from scratch.

  • Tag added to subscriber in ConvertKit creates Create Event in customer.io

    Trigger when a tag is added to a subscriber

  • Tag added to subscriber in ConvertKit creates Track Custom API Call in customer.io

    Trigger when a tag is added to a subscriber

  • Tag added to subscriber in ConvertKit creates App Custom API Call in customer.io

    Trigger when a tag is added to a subscriber

  • Tag removed from subscriber in ConvertKit creates Create Event in customer.io

    Trigger when a tag is removed from a subscriber

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in customer.io and acts in ConvertKit, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.