Skip to content
Uscreen logoConvertKit logo

Connect Uscreen to ConvertKit

Move data between Uscreen 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.

Uscreen triggers
5
Uscreen actions
3
ConvertKit triggers
12
ConvertKit actions
35

Automation ideas

What you can build with Uscreen and ConvertKit

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

  • Paid Order in Uscreen creates Get Subscriber By Id in ConvertKit

    Triggers when a payment is processed for subscriptions, bundles, or content.

  • Tag added to subscriber in ConvertKit creates Create User in Uscreen

    Trigger when a tag is added to a subscriber

  • Paid Order in Uscreen creates Get Subscriber By Email in ConvertKit

    Triggers when a payment is processed for subscriptions, bundles, or content.

  • Tag added to subscriber in ConvertKit creates Assign User Access in Uscreen

    Trigger when a tag is added to a subscriber

  • Paid Order in Uscreen creates List Subscribers in ConvertKit

    Triggers when a payment is processed for subscriptions, bundles, or content.

  • Tag added to subscriber in ConvertKit creates Custom API Call in Uscreen

    Trigger when a tag is added to 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 Uscreen 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.