Skip to content
ConvertKit logoDrip logo

Connect ConvertKit to Drip

Move data between ConvertKit and Drip 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
36
Drip triggers
2
Drip actions
4

Automation ideas

What you can build with ConvertKit and Drip

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

  • Tag added to subscriber in ConvertKit creates Apply a tag to subscriber in Drip

    Trigger when a tag is added to a subscriber

  • New Subscriber in Drip creates Get Subscriber By Id in ConvertKit

    Triggers when a subscriber is created in your Drip account.

  • Tag added to subscriber in ConvertKit creates Add a subscriber to a campaign in Drip

    Trigger when a tag is added to a subscriber

  • New Subscriber in Drip creates Get Subscriber By Email in ConvertKit

    Triggers when a subscriber is created in your Drip account.

  • Tag added to subscriber in ConvertKit creates Create or Update Subscriber in Drip

    Trigger when a tag is added to a subscriber

  • New Subscriber in Drip creates List Subscribers in ConvertKit

    Triggers when a subscriber is created in your Drip account.

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 Drip, 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.