FlowRunner
PricingContact
Theme
Start Free

ChartMogul

Analytics & Data

Pull subscription analytics from ChartMogul into your flows. Agents read MRR, ARR, churn, and LTV metrics, manage customers, plans, and invoices in Import API data sources, push subscription events, and alert when revenue metrics cross thresholds.

39 actions Basic auth available
ChartMogul website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
Daily 6am run pulls the previous day's revenue movements
Get MRR returns new business, expansion, contraction, and churn
Get Customer Churn Rate confirms the movement against the trend
Churned MRR compared to the monthly alert threshold
List Customers resolves the accounts behind the churn movement
Slack post names the churned accounts and their MRR impact
Finance owner decides which accounts get a save play before outreach

What This Integration Enables

ChartMogul is the number the board sees. Which means the real job is not reading it, it is keeping it honest and acting on it the day it moves. Agents work both directions. On the way in, they maintain Import API data sources: creating customers, plans, and subscription events, importing invoices, and backfilling history so the MRR engine reflects what billing actually did. On the way out, they pull MRR, ARR, ARPA, ASP, churn rates, customer counts, and LTV on a schedule, break MRR into its movements, and resolve the specific accounts behind a change with customer lookups by email or UUID. The stance this connector takes is that revenue metrics should open workflows, not decorate dashboards. A churn spike that surfaces at month end is a report. The same spike surfaced the next morning, with the accounts named and a [human-in-the-loop](/concepts/human-in-the-loop/) decision on which ones get a save play, is an operation. Connector capabilities are built and verified against ChartMogul's official API.

Without FlowRunner

Month-end surprises Churn shows up in the board deck weeks after the customers left
Metrics on request Someone exports MRR by hand every time a stakeholder asks
Drifting billing data The Import API source and the billing system quietly disagree

With FlowRunner

Same-day churn visibility Every churn movement is named, sized, and posted the morning after
Self-maintaining reporting MRR, ARR, churn, and LTV land in the dashboard on a schedule
Reconciled sources Subscription state is compared across systems and drift gets flagged

Use Case Scenarios

The churn movement that gets a same-day response

A daily agent calls Get MRR with the movement breakdown and Get Customer Churn Rate for trend context. When churned MRR crosses the alert threshold, it resolves the specific accounts with List Customers and List Customer Subscriptions, then posts to the revenue channel in [Slack](/integrations/slack): the accounts, their MRR, their plan, and their tenure. The finance owner picks which accounts warrant a save attempt and which are closed business. Outreach starts while the cancellation is days old, not weeks.

Keeping the MRR engine fed from billing

When a subscription is created or changed in [Stripe](/integrations/stripe), an agent mirrors it into a ChartMogul Import API source: Create Customer if Search Customers by Email finds no match, then Create Subscription Event to record the lifecycle change that drives the MRR calculation. On a weekly schedule, a reconciliation pass compares subscription state in [Chargebee](/integrations/chargebee) or Stripe against List Customer Subscriptions and flags accounts whose state has drifted between systems. The metric everyone trusts stays trustworthy because something is checking it.

Board metrics without the export ritual

A scheduled agent calls Get All Metrics for the trailing period and appends MRR, ARR, ARPA, customer count, churn rates, and LTV to a running workbook with [Google Sheets](/integrations/google-sheets). Before the monthly business review, it posts the summary with the largest movements called out. The FP&A analyst who used to assemble this by hand now spends the same hour on the question the numbers raise instead of the numbers themselves.

Human-in-Loop Highlight

Delete Data Source permanently deletes every customer, plan, subscription, and invoice imported through that source, and ChartMogul cannot restore any of it. It is exactly the operation a cleanup workflow wants to run and exactly the one it must not run alone. When an agent finds a stale or duplicate Import API source polluting MRR, it gathers the evidence first: the source's customer count from List Customers, its subscription events, and whether any current metrics still draw from it. Then it asks the finance owner directly: "Data source 'stripe-test-import' holds 41 customers and last received an event in November. Deleting it removes all of its imported data permanently. Confirm deletion, or keep and exclude from reporting?" The agent stages the cleanup. The person who answers for the MRR number executes it.

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

Agent Capabilities

39 actions

Customers

8
  • List Customers Lists customers filtered by data source, external ID, or subscription status. Used to resolve the accounts behind a metric movement.
  • Get Customer Retrieves a customer by UUID with status, MRR, ARR, lifetime value, and billing attributes. Used to size an account before a decision about it.
  • Search Customers by Email Finds all customers matching an email across data sources. Used for lookups and duplicate checks before creating records.
  • Create Customer Creates a customer in a data source with an external ID. Used when mirroring billing systems into an Import API source.
  • Update Customer Updates a customer's editable attributes, including tags and custom fields. Used to enrich accounts with workflow context.
  • Delete Customer Permanently deletes a customer and all associated subscriptions, invoices, and events. Cannot be undone; routed through human approval.
  • List Customer Contacts Lists the people associated with a customer, with contact details. Used to route save plays to a real person.
  • List Customer Subscriptions Lists a customer's subscriptions with plan, quantity, MRR, and dates. Used in churn investigation and cross-system reconciliation.

Data Sources

4
  • List Data Sources Lists all data sources with their originating system and import status. Used to audit where the MRR number comes from.
  • Get Data Source Retrieves a single data source with its status and creation time.
  • Create Data Source Creates a manual Import API data source. Used before importing customers, plans, and invoices from a system ChartMogul does not natively connect.
  • Delete Data Source Permanently deletes a data source and everything imported through it. The gated action in this connector: a human confirms before anything is removed.

Plans

5
  • List Plans Lists billing plans, optionally filtered by data source or external ID.
  • Get Plan Retrieves a plan with its billing interval and data source.
  • Create Plan Creates a billing plan in a data source with its interval and price basis. Used when mirroring a billing catalog.
  • Update Plan Updates a plan's name.
  • Delete Plan Permanently deletes a plan that has no subscriptions attached. Used in catalog cleanup.

Plan Groups

6
  • List Plan Groups Lists plan groups that bundle related plans for combined reporting.
  • Get Plan Group Retrieves a plan group with its plan count.
  • List Plans in Group Lists the plans inside a group. Used to verify reporting rollups.
  • Create Plan Group Creates a plan group from a set of plan UUIDs, such as monthly and annual variants of one product.
  • Update Plan Group Updates a group's name or membership.
  • Delete Plan Group Permanently deletes the grouping. The plans themselves are untouched.

Invoices

2
  • List Invoices Lists invoices with line items and transactions, filterable by data source or customer. Used in revenue reconciliation.
  • Import Invoices Imports invoices for a customer through the Import API. Used to backfill billing history into the MRR engine.

Subscription and Customer Events

4
  • List Subscription Events Lists subscription lifecycle events for a data source. Used to audit what has been fed to the MRR engine.
  • Create Subscription Event Records a subscription start, update, or cancellation in a data source. The write that keeps ChartMogul in sync with billing.
  • List Customer Events Lists customer events for a data source.
  • Create Customer Event Records a non-subscription customer lifecycle change or custom activity.

Metrics

9
  • Get All Metrics Retrieves MRR, ARR, ARPA, ASP, customer count, churn rates, and LTV for a date range in one call. Used for scheduled reporting.
  • Get MRR Retrieves MRR broken into new business, expansion, contraction, churn, and reactivation. The movement breakdown that drives the daily digest.
  • Get ARR Retrieves annualized run rate over a date range.
  • Get ARPA Retrieves average revenue per account over a date range.
  • Get ASP Retrieves the average MRR of newly acquired customers per interval.
  • Get Customer Count Retrieves active paying customer counts over a date range.
  • Get MRR Churn Rate Retrieves net MRR churn as a percentage, where negative values mean net expansion. Used for threshold alerts.
  • Get Customer Churn Rate Retrieves the percentage of customers lost over a date range. Used to confirm whether a movement is trend or noise.
  • Get LTV Retrieves estimated customer lifetime value over a date range.

Account

1
  • Get Account Retrieves the account's name, currency, and time zone. Used to verify the connection and interpret amounts correctly.

Frequently Asked Questions

What can FlowRunner do with ChartMogul?

FlowRunner agents can run List Customers, Get Customer, and Search Customers by Email in ChartMogul, plus 36 more actions.

Does connecting ChartMogul to FlowRunner require OAuth?

No. ChartMogul connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can ChartMogul trigger a FlowRunner workflow automatically?

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

Start building with ChartMogul

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