Skip to content
RevenueCat logo

RevenueCat integration

Finance & Payments · 10 actions · API key auth

Manage in-app subscriptions and entitlements. Retrieve customer subscription status, grant or revoke promotional entitlements, record purchases, update subscriber attributes, and manage Google Play subscription billing.

The ModuleX RevenueCat integration lets a ModuleX agent operate RevenueCat on your behalf, running create, update and remove actions across customers, purchases and grant entitlements, directly from a plain-English request, using your organization's own RevenueCat credentials. No pre-built workflow is required: the agent picks the right RevenueCat action for the task.

RevenueCat is a finance & payments platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right RevenueCat action. Or, when you want a repeatable process, the composer assembles a RevenueCat workflow for you, streaming the nodes onto the canvas as it builds.

Drive RevenueCat in plain English

Type what you want. A ModuleX agent picks the right RevenueCat action, or chains several, and runs it. No workflow to build.

  • Record a purchase (receipt) for a subscriber via the REST API
    resolves tocreate_purchase
  • Find the customer I describe and remove it
    resolves toget_customerdelete_customer
  • Update custom subscriber attributes (e.g., $email, $displayName, or custom key-value pairs)
    resolves toupdate_subscriber_attributes
  • Show me the offerings that match what I describe
    resolves tolist_offerings

What you can automate with RevenueCat

  • Find the right customer and remove it in one promptget_customerdelete_customer
  • Create a purchase straight from a requestcreate_purchase
  • Pull a list of offerings for a reportlist_offerings
  • Update a subscriber attribute the moment something changesupdate_subscriber_attributes

RevenueCat integration at a glance

Actions available10
AuthenticationAPI key
Uses your own credentialsYes
Works with the assistantYes
Works in the composerYes
Multi-step / tool-chainingYes
Technical referenceView docs
Integration version1.0.0
Last updatedJul 2026

All 10 RevenueCat actions

Customers2
get_customer
Retrieve subscriber information by app user ID.
delete_customer
Permanently delete a subscriber and all associated data.
Purchases1
create_purchase
Record a purchase (receipt) for a subscriber via the REST API.
Grant Entitlements1
grant_entitlement
Grant a promotional entitlement to a subscriber.
Revoke Entitlements1
revoke_entitlement
Revoke all promotional entitlements for a specific entitlement identifier.
Offerings1
list_offerings
List all offerings configured for the project.
Subscriber Attributes1
update_subscriber_attributes
Update custom subscriber attributes (e.g., $email, $displayName, or custom key-value pairs).
Defer Google Subscriptions1
defer_google_subscription
Defer a Google Play subscription by extending its billing date (Google Play only).
Google Subscriptions1
refund_google_subscription
Refund a specific store transaction by its store transaction identifier and revoke access (subscription or non-subscription, last 365 days).
Revoke Google Subscriptions1
revoke_google_subscription
Immediately revoke access to a Google Play subscription and issue a refund (Google Play only).

See full parameters and response schemas in the RevenueCat integration docs

Two ways to use RevenueCat in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right RevenueCat action and runs it. No workflow to build.
Compose a workflowNeed it to happen every time? Describe the process and the composer wires RevenueCat into a repeatable workflow you can run on a schedule, from chat, or as an API.

Connecting RevenueCat

API keyRevenueCat uses API-key authentication. You provide your own RevenueCat secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use RevenueCat without re-authenticating.

Step-by-step setup in the RevenueCat docs

Works with RevenueCat

Agents often chain RevenueCat with these. Connect them once and one agent can use all of them in a single task.

RevenueCat + ModuleX FAQ

  • A ModuleX agent can run any of RevenueCat's 10 actions, across customers, purchases, grant entitlements and revoke entitlements, from a plain-English request, using your organization's own RevenueCat credentials.

Put RevenueCat to work in ModuleX.

Connect RevenueCat once with your own credentials and let your agent run all 10 actions on demand.

Last updated: Jul 2026Browse all 179 integrations