Hotmart
E-commerceConnect AI agents to Hotmart, the digital product sales platform. Agents pull sales history, summaries, participants, and commissions, monitor and cancel subscriptions, and list products to reconcile creator revenue.
What This Integration Enables
A creator business on Hotmart is really three ledgers wearing one dashboard: sales, recurring subscriptions, and the commission splits that pay everyone involved. This connector gives FlowRunner agents a clean read of all three, plus one carefully guarded write. Agents pull sales history and summaries, reconcile participant commissions, monitor subscription status for retention plays, and cancel subscriptions when a verified request demands it, so revenue operations stop being an evening job that competes with making the product. - Sync approved sales and transaction detail into spreadsheets, the CRM, or a warehouse - Report recurring-revenue metrics from sales and subscription summaries - Reconcile producer, co-producer, and affiliate commissions per transaction - Trigger follow-ups when a sale or a cancellation happens - Cancel a subscriber's recurring plan inside a governed workflow - Look up product IDs, statuses, and formats across the catalog The cancellation is the sharp edge, and it is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration holds the line: stopping someone's recurring revenue is a decision, not a step. The shape of this connector rewards a particular operating rhythm: read constantly, write almost never. Creator businesses live and die on the trust between producer, co-producers, and affiliates, and that trust is really an accounting claim, everyone believes the splits are right. An agent that verifies every split every week, and produces the evidence trail when someone asks, is cheaper than the first serious partner dispute. The same rhythm serves the subscription side: statuses read daily become retention signals; statuses read at month end are churn autopsies. FlowRunner agents make the constant reading free, which changes which questions get asked at all.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The sales ledger that fills itself
Nightly, List Sales History pulls the day's approved transactions and each one lands in [Google Sheets](/integrations/google-sheets) with buyer, product, price, and commission detail. Get Sales Summary appends the day's aggregates, gross, net, fees, and the agent posts the digest to [Slack](/integrations/slack). Month end stops being an export marathon: the ledger already exists, row by row, from the day the month started.
New subscribers enter the nurture flow the same day
A scheduled sweep of List Subscriptions catches newly active subscribers. Each one flows into [Klaviyo](/integrations/klaviyo) with plan and product context, entering the onboarding sequence that turns a purchase into a habit. Subscribers whose status shifts toward risk get flagged for the retention track instead. The list the marketing runs on and the truth the platform holds stop drifting apart.
Commission reconciliation before the dispute
Weekly, the agent walks List Sales Commissions for every transaction in the window and checks each split, producer share, co-producer share, affiliate cut, against the expected terms. Deviations are itemized: which transaction, whose commission, expected versus actual. List Sales Participants attaches who was involved. The finance owner reviews five flagged rows instead of five hundred raw ones, and partner payout disputes get settled with evidence before they become disputes at all.
Human-in-Loop Highlight
Cancel Subscription stops a subscriber's future recurring charges, and the action cannot be undone: if it fires on the wrong subscriber code, there is no reinstate call, only an apology and a hope they re-subscribe. That asymmetry defines the workflow. The agent handles everything reversible, finding the subscription with List Subscriptions, pulling plan and next-charge detail, verifying the requester matches the subscriber, and then stops. The person who owns retention sees the subscriber code, the plan, the revenue ending, and the optional cancellation notice email, and gives the explicit yes. Only then does Cancel Subscription execute, with the outcome logged and the retention team notified. Machine speed for the lookup, human judgment for the goodbye. That division of labor is the whole design, applied at the one point where this connector can end a revenue stream.
Agent Capabilities
8 actionsSales
4- List Sales History Retrieves individual transactions with buyer, product, price, commission, and status, filterable by date range, status, product, and buyer email. Date filters use epoch-millisecond timestamps. The transaction-level read behind the ledger.
- Get Sales Summary Retrieves aggregate figures for a period: gross, net, fees, taxes, and transaction counts. The cross-check that validates transaction-level math and feeds dashboards.
- List Sales Participants Retrieves the people involved in each sale: buyers, producers, co-producers, and affiliates. The evidence read behind payout questions.
- List Sales Commissions Retrieves how each transaction's value splits between producer, co-producers, and affiliates, with the commissioned user and amount. The engine of commission reconciliation.
Subscriptions
3- List Subscriptions Retrieves subscriptions with subscriber, plan, status, and next-charge detail, filterable by subscriber code, status, product, or plan. The sweep behind retention monitoring.
- Get Subscriptions Summary Retrieves aggregate subscription figures: counts by status, active recurrences, totals. The recurring-revenue snapshot without paging every subscriber.
- Cancel Subscription Cancels an active subscription by subscriber code, stopping future charges, with an optional notice email. Cannot be undone. The operation this page's human gate exists for.
Catalog
1- List Products Retrieves the account's digital products, courses, e-books, memberships, with ID, name, status, and format. The reference read that keys reporting and filtering across every other action.
Frequently Asked Questions
What can FlowRunner do with Hotmart?
FlowRunner agents can run List Sales History, Get Sales Summary, and List Sales Participants in Hotmart, plus 5 more actions.
Does connecting Hotmart to FlowRunner require OAuth?
Yes. Hotmart connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Hotmart trigger a FlowRunner workflow automatically?
Hotmart doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Hotmart
$100 in credits. No card required. Connect in minutes.