Skip to content
ConvertKit logoPromoteKit logo

Connect ConvertKit to PromoteKit

Move data between ConvertKit and PromoteKit 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.

ConvertKit triggers
12
ConvertKit actions
35
PromoteKit triggers
3
PromoteKit actions
14

Automation ideas

What you can build with ConvertKit and PromoteKit

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

  • Tag added to subscriber in ConvertKit creates List Affiliates in PromoteKit

    Trigger when a tag is added to a subscriber

  • New Affiliate Event in PromoteKit creates Get Subscriber By Id in ConvertKit

    Triggers when a PromoteKit affiliate event is received.

  • Tag added to subscriber in ConvertKit creates Find Affiliate in PromoteKit

    Trigger when a tag is added to a subscriber

  • New Affiliate Event in PromoteKit creates Get Subscriber By Email in ConvertKit

    Triggers when a PromoteKit affiliate event is received.

  • Tag added to subscriber in ConvertKit creates Create Affiliate in PromoteKit

    Trigger when a tag is added to a subscriber

  • New Affiliate Event in PromoteKit creates List Subscribers in ConvertKit

    Triggers when a PromoteKit affiliate event is received.

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 ConvertKit and acts in PromoteKit, 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.