FlowRunner
PricingContact
Theme
Start Free

Keep Kartra in sync with the rest of your stack. Agents create and update leads, assign and remove tags to drive Kartra automations, subscribe contacts to mailing lists, and grant membership site access after a purchase.

7 actions API key available
Kartra website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A course purchase completes in the external storefront
Agent verifies the payment actually settled in the payment processor
Create Lead adds or refreshes the buyer in Kartra, keyed on email
Assign Tag applies the buyer tag that starts the post-purchase sequence
Subscribe To List places the buyer on the customer newsletter
Access grants the agent cannot tie to a settled payment, a refund in flight, a mismatched email, wait for a person
Grant Membership provisions the course access once cleared
The operations channel logs the buyer, the payment reference, and the access granted

What This Integration Enables

Kartra bundles the funnel, the email sequences, and the membership site into one machine, and the machine runs on two inputs: what a lead's record says, and which tags it carries. Businesses that sell only through Kartra's own checkout get those inputs for free. Everyone else, selling through Shopify, Stripe, webinars, or a sales team, has a gap between where money changes hands and where access and automation live. FlowRunner agents close that gap, with the one write that gives away the product held behind a human gate. - Create or update leads whenever a form is submitted or an order is placed anywhere in the stack - Tag and segment contacts to drive Kartra automations and email sequences - Subscribe contacts to mailing lists and nurture sequences - Grant membership site access after a verified purchase or approved manual enrollment - Look up a lead's full profile, tags, lists, and memberships, before taking further action Tags in Kartra are automation triggers, and memberships are the product itself. Both writes get the respect they deserve through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline. Email-keyed identity is the quiet advantage here. Because Kartra resolves every lead by email address, FlowRunner flows never juggle foreign IDs between systems: the same address that identifies the customer in Stripe, Shopify, or a form response identifies them in Kartra, and Create Lead's built-in upsert behavior means repeated events converge on one record instead of manufacturing duplicates. Sync logic stays simple, and simple sync logic is the kind that still works a year later.

Without FlowRunner

Purchases outside Kartra provision by hand Buyers from other checkouts wait hours for course access while someone works through the enrollment queue
Tags depend on memory Segmentation happens when a human remembers to tag, so sequences fire late or on the wrong people
The lead record is partial Kartra sees what happened inside Kartra, and everything from the CRM, store, and forms stays invisible

With FlowRunner

Access follows payment in minutes Verified purchases provision membership access automatically, any hour of any day
Tags fire at the moment of the event Every source applies its segment tag on arrival, and Kartra's automations take over from there
The whole stack feeds the lead Forms, stores, and payment systems create and update leads continuously, keyed on email

Use Case Scenarios

The course purchase that provisions itself

A buyer completes checkout in [Shopify](/integrations/shopify). The agent confirms the order is paid, calls Create Lead with the buyer's details, applies the course tag with Assign Tag, and calls Grant Membership for the matching membership site. The buyer's welcome email from Kartra's own automation arrives with working login access, minutes after payment, at 2 AM on a Sunday if that is when they bought.

Webinar registrants segmented before the replay goes out

Registrations flow in from [Typeform](/integrations/typeform). The agent creates each registrant with Create Lead, tags them by the interest they selected, and subscribes them to the webinar list with Subscribe To List. After the event, attendance data updates the tags: attended one tag, no-show another. Kartra's sequences then speak to each group differently, and the replay email writes itself into the right inboxes.

Stripe subscribers who never fall through the crack

A new customer appears in [Stripe](/integrations/stripe). The agent checks Get Lead for an existing record, creates or updates the lead, subscribes them to the customer nurture list, and logs the pairing of Stripe customer ID to Kartra lead in [Google Sheets](/integrations/google-sheets). When a subscription lapses, Remove Tag pulls the active-customer tag so win-back automation takes over. Revenue state and marketing state finally agree.

Human-in-Loop Highlight

Grant Membership hands out the thing customers pay for. One call, identified by nothing more than an email and a membership name, and a person has full access to the course or community; there is no invoice check built into the API, and access granted wrongly is revenue you will spend support cycles clawing back, if you claw it back at all. So FlowRunner flows bind that call to evidence: the agent grants only when it holds a settled payment reference from the processor, and everything else stops. A chargeback filed minutes after purchase, an enrollment request from an email that matches no payment, a typo'd address that would provision a stranger: each posts to the operations channel as "Grant blocked: no settled payment found for [email protected] against Creator Academy. Approve manually or investigate?" A person decides. The adjacent trap gets the same care: Assign Tag silently creates any tag that does not exist, so agents tag only from a maintained vocabulary, because a misspelled tag does not error, it quietly forks your segmentation.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

7 actions

Leads

3
  • Create Lead Creates a lead with email and optional profile details. Kartra keys leads on email, so an existing address is updated rather than duplicated, making this the safe default write for every source.
  • Get Lead Retrieves a lead's full profile by email: ID, contact fields, tags, subscribed lists, and membership access. The context read before tagging, granting, or updating.
  • Update Lead Updates profile fields on an existing lead by email, changing only the fields supplied. The enrichment write for syncs from the CRM and store.

Tags

2
  • Assign Tag Assigns a tag to a lead by email, creating the tag automatically if it does not exist. Tags trigger Kartra automations, so FlowRunner agents assign only from an approved vocabulary.
  • Remove Tag Removes a tag from a lead, reversing the segmentation or automation trigger tied to it. Removing an absent tag is a no-op, which makes it safe in cleanup sweeps.

Lists

1
  • Subscribe To List Subscribes a lead to an existing mailing list by name. The opt-in step for newsletters and nurture sequences.

Memberships

1
  • Grant Membership Grants a lead access to an existing membership site by name. The operation this page's human gate exists for: it provisions the product itself.

Frequently Asked Questions

What can FlowRunner do with Kartra?

FlowRunner agents can run Create Lead, Get Lead, and Update Lead in Kartra, plus 4 more actions.

Does connecting Kartra to FlowRunner require OAuth?

No. Kartra connects to FlowRunner with an API key, no OAuth flow required.

Can Kartra trigger a FlowRunner workflow automatically?

Kartra doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Kartra

$100 in credits. No card required. Connect in minutes.