--- title: "Kajabi Integration" description: "Connect AI agents to Kajabi. Agents manage contacts and tags, grant or revoke offers, and read products, courses, purchases, orders, and forms to automate enrollment and follow-up across your knowledge commerce business." url: https://flowrunner.ai/integrations/kajabi date_modified: 2026-08-04T10:04:16-07:00 --- # Kajabi [Education & LMS](https://flowrunner.ai/integrations/category/education-lms) Connect AI agents to Kajabi. Agents manage contacts and tags, grant or revoke offers, and read products, courses, purchases, orders, and forms to automate enrollment and follow-up across your knowledge commerce business. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 29 actions · OAuth · available [Kajabi website](https://kajabi.com/) · [Platform Documentation](https://developers.kajabi.com/) · Capability data verified 2026-08-12 1. A completed purchase lands from the external checkout or CRM 2. Agent reads the buyer's email and the offer they bought 3. List Contacts confirms whether the buyer already exists on the site 4. Create Contact if needed, then Grant Offer to Contact enrolls them in the course 5. Agent confirms the granted offer now appears on the contact 6. The team channel gets the enrollment summary; the grant's welcome email handles the student 7. A grant with no matching payment on record, a comp or an ambiguity, waits for the owner before access is handed out ## What This Integration Enables In a Kajabi business, access is the product. A granted offer is not a CRM field; it is the thing the customer paid for. FlowRunner agents treat it that way. They manage contacts and tags, grant and revoke offers to control enrollment, and read the commercial spine of the site: products, courses, purchases, orders, and forms. That makes the connector the bridge between wherever your sales actually happen, an external checkout, a CRM, a funnel tool, and the place where the student receives what they bought. Because grants and revokes are revenue moves, FlowRunner splits them by consequence. Granting a paid-for offer is routine and runs unattended. Granting an offer nobody paid for, revoking a student's access, or permanently deleting a contact are decisions, and the flow routes each to a person with the evidence assembled. ### Without FlowRunner **Enrollment by CSV**: Buyers from external checkouts imported by hand, sometimes days after they paid **Access decisions in the dark**: Failed payments and refunds leave course access on, or yank it, with no consistent rule **Segments gone stale**: Tags reflect where students were the last time someone did a cleanup pass ### With FlowRunner **Enrolled the moment they pay**: Purchase lands, contact exists, offer granted, welcome email out **Access changes with evidence**: Every revoke proposed with the payment history attached and approved by a person **Tags that track behavior**: Segment membership updated continuously from activity in other systems ## Use Case Scenarios ### Deal closed, student enrolled A deal closes in [HubSpot](https://flowrunner.ai/integrations/hubspot). The agent checks List Contacts on the Kajabi site for the buyer's email, calls Create Contact if they are new, and matches the purchased line item to the right offer via List Offers. Grant Offer to Contact enrolls them, Kajabi's welcome email goes out, and the agent verifies the grant landed before marking the CRM record fulfilled. The gap between paid and enrolled, where refund requests are born, disappears. ### Segments synced from behavior Activity tracked in other systems, webinar attendance, quiz completion, purchase tier, flows back as tags. The agent resolves tag IDs with List Tags, applies them with Add Tag to Contact, and clears outdated ones with Remove Tag from Contact. It then mirrors the segments into [Mailchimp](https://flowrunner.ai/integrations/mailchimp-marketing) so email campaigns target students by what they actually did. Because Kajabi's API does not create tags on demand, the agent flags any missing tag for the team to create in the dashboard rather than silently skipping it. ### Failed payment, access reviewed by a person The external biller reports a subscription payment failed twice. The agent gathers the contact, their purchase history from List Purchases, and their engagement, then posts to the owner: revoke now, or hold while the customer is contacted? Only after the owner answers does Revoke Offer from Contact run, or not run. Either way the decision and its reasoning are logged, and the revenue log in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) stays reconciled against List Orders. ## Human-in-Loop Highlight Revoke Offer from Contact removes a student's access to the products behind an offer, immediately. Used carelessly, it locks a paying customer out of a course mid-module over a card that expired on vacation. So the FlowRunner dunning agent never revokes on a signal alone. It assembles the case and asks the owner: "Payment for 'Advanced Program' by r.silva failed twice at the biller. Purchase history shows 14 months of on-time payments. Revoke access now, or hold access while a payment-update email goes out?" The owner picks the hold, the recovery email goes out, and access survives a billing hiccup that was never a cancellation. If the owner says revoke, the agent revokes and records who decided. The judgment call about a customer relationship stays with the person who owns the relationship; that is the whole point of [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) enrollment control. 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 29 actions ### Sites 2 - **List Sites** Discover the Kajabi sites the connected credentials reach. Most operations are site-scoped, so this is where every flow starts. - **Get Site** Load one site's details before running site-scoped operations. ### Contacts 5 - **List Contacts** Search people by name, email, or tag, offer, and product membership. The dedupe check before every create. - **Get Contact** Load one contact with full attributes and relationships. - **Create Contact** Add buyers as contacts, with email required. - **Update Contact** Update only the fields provided. - **Delete Contact** Permanently delete a contact. Cannot be undone, so erasure flows route it through a named approver. ### Tags 4 - **Add Tag to Contact** Apply segment membership using an existing tag. Kajabi's API does not create tags, so flows surface missing tags instead of failing silently. - **Remove Tag from Contact** Clear a tag when the behavior behind it no longer holds. - **List Tags** Resolve tag names to IDs, the reference data behind every segmentation flow. - **Get Tag** Load one tag by ID. ### Offers and Enrollment 4 - **List Offers** Read the site's active offers with price, payment type, and checkout URL, and match purchased items to the offer that fulfills them. - **Get Offer** Load one offer's detail before granting it. - **Grant Offer to Contact** Enroll a contact, creating the customer if needed and sending the welcome email unless suppressed. The fulfillment step of every external sale. - **Revoke Offer from Contact** Remove access to an offer's products. The revenue-relationship move a person approves. ### Products and Courses 4 - **List Products** Read active products with status and member counts, for reporting and access audits. - **Get Product** Load one product's detail and membership. - **List Courses** Read courses with publish status. - **Get Course** Load one course, expanding modules and lessons when a flow needs the structure. ### Commerce Records 4 - **List Purchases** Read offer grants bought or received, filtered by status, referrer, coupon, and customer. The evidence base for access decisions. - **Get Purchase** Load one purchase record in full. - **List Orders** Read orders with fulfillment status for revenue logging and reconciliation. - **Get Order** Load one order's amounts and status. ### Forms 2 - **List Forms** Enumerate opt-in and marketing forms, used to connect form activity to segmentation. - **Get Form** Load one form's fields and settings. ### Webhooks 4 - **List Webhooks** Enumerate the hooks a Kajabi site delivers events through. - **Create Webhook** Subscribe a target URL to a chosen event, configuring Kajabi's outbound notifications to systems a flow maintains. - **Get Webhook** Read one hook's event and target URL. - **Delete Webhook** Remove a hook that should stop firing. ## Frequently Asked Questions ### What can FlowRunner do with Kajabi? FlowRunner agents can run List Sites, Get Site, and List Contacts in Kajabi, plus 26 more actions. ### Does connecting Kajabi to FlowRunner require OAuth? Yes. Kajabi connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Kajabi trigger a FlowRunner workflow automatically? Kajabi doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Kajabi?** This integration exposes Kajabi to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/kajabi. Site index: https://flowrunner.ai/llms.txt