Skip to content
Wistia logoConvertKit logo

Connect Wistia to ConvertKit

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

Wistia triggers
2
Wistia actions
8
ConvertKit triggers
12
ConvertKit actions
35

Automation ideas

What you can build with Wistia and ConvertKit

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

  • New Media in Wistia creates Get Subscriber By Id in ConvertKit

    Triggers when a new video or media file is added to your account.

  • Tag added to subscriber in ConvertKit creates Create Project in Wistia

    Trigger when a tag is added to a subscriber

  • New Media in Wistia creates Get Subscriber By Email in ConvertKit

    Triggers when a new video or media file is added to your account.

  • Tag added to subscriber in ConvertKit creates Update Project in Wistia

    Trigger when a tag is added to a subscriber

  • New Media in Wistia creates List Subscribers in ConvertKit

    Triggers when a new video or media file is added to your account.

  • Tag added to subscriber in ConvertKit creates Get Media in Wistia

    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 Wistia 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.