Skip to main content
Connect RevenueCat so in-app purchase and subscription events fire Brew automations across every billing platform. The same lifecycle email flow can serve Apple App Store, Google Play, Amazon, Stripe, and Web Billing subscribers without per-store glue code.
  • Trigger automations from RevenueCat events. Welcome new paid customers, win-back during cancellation grace periods, re-engage after expiration, drip dunning on billing issues.
  • Auto-sync subscribers into your audience. Every RevenueCat event upserts the subscriber into Brew with revenuecat-prefixed custom fields (revenuecatSubscriptionStatus, revenuecatProductId, etc.) you can filter and segment on.
  • Cover every store with one connection. App Store, Play Store, Amazon, Stripe, Web Billing: RevenueCat normalizes receipts, Brew normalizes triggers.
  • Personalize with product context. Reference plan, price, store, and cancellation reasons inside emails.
RevenueCat webhooks are part of the Pro plan, which is free up to $2,500 in monthly tracked revenue. Older legacy plans without webhooks need to move to Pro.
Every marketing recipient must have opted in to hear from you. Importing or syncing contact data into Brew is not permission to email it. See What You Can Send.

How It Works

RevenueCat works like every other event source. Brew gives you a webhook URL and verifies each delivery. Each verified event starts the matching Live automations and upserts the subscriber into your audience with revenuecat-prefixed fields. Connected-Source Events has the full model. What’s RevenueCat-specific: you turn on HMAC signing in RevenueCat and paste the one-time signing secret into Brew. Brew checks the timestamped X-RevenueCat-Webhook-Signature header against it, with a replay window. The $email subscriber attribute becomes the contact’s email.

Setup

1

Generate your Brew webhook URL

In Brew, open Integrations, click the RevenueCat card, open the Setup tab, and click Generate webhook URL. Copy the URL Brew generates.
2

Add the webhook in RevenueCat and enable HMAC signing

Open app.revenuecat.com and select your project. In the left menu, go to Integrations → Webhooks and click Add new configuration. Then set:
  • Name: any label, such as “Brew”
  • Webhook URL: the Brew URL from step 1
  • Environment: production, sandbox, or both
  • App: one app or all apps in the project. Brew only receives events for the apps you pick.
Save, then enable HMAC webhook signing on the configuration. RevenueCat shows the signing secret once, so copy it before closing the dialog.
3

Paste the signing secret into Brew

Paste the signing secret into the Brew connect form and click Connect. Brew verifies the timestamped X-RevenueCat-Webhook-Signature header on every webhook against this secret.
4

Verify it's working

Make a sandbox purchase, or send a test event from the webhook configuration in the RevenueCat dashboard. Within a few seconds it should appear in Manage → Recent events on the RevenueCat integration page in Brew. If it doesn’t, re-generate the HMAC signing secret in RevenueCat and reconnect Brew with the new value.
RevenueCat doesn’t include user emails on most events by default. Set the $email attribute right after sign-in so Brew can resolve the real recipient. Without it, automations fan out to a placeholder address.
  • iOS (Swift): Purchases.shared.attribution.setEmail(email)
  • Android (Kotlin): Purchases.sharedInstance.setEmail(email)
  • Flutter and React Native: Purchases.setEmail(email)
  • Web: Purchases.getSharedInstance().setAttributes({ [ReservedCustomerAttribute.Email]: email })

Supported Events

Once connected, every RevenueCat event below is provisioned automatically and available as a trigger in the automation builder. The Manage tab shows:
  • Webhook URL: the URL your RevenueCat webhooks point at
  • RevenueCat events: how many events Brew has received, and each event’s status
  • Recent events: up to 25 of the newest deliveries that passed the signature check
Once Brew has received an event, it reads Last event and how long ago. It reads No events yet if it hasn’t fired. No events in 90 days means none arrived in the last 90 days, which is how long Brew keeps each delivery. If an event reads No trigger, click Re-provision. There’s no per-event enable step. An event fires only when its bound automation is Live. Brew supports the following 11 RevenueCat events: Purchase
  • INITIAL_PURCHASE
  • NON_RENEWING_PURCHASE
Subscription
  • RENEWAL
  • PRODUCT_CHANGE
  • CANCELLATION
  • UNCANCELLATION
  • EXPIRATION
  • SUBSCRIPTION_PAUSED (Google Play only)
  • SUBSCRIPTION_EXTENDED
  • TRANSFER
Billing
  • BILLING_ISSUE
CANCELLATION doesn’t revoke access. It only signals intent. Use it to drip win-back during the grace period. Wait for the matching EXPIRATION event before deactivating user-facing features.
In chat, say “Send a dunning email when a payment fails”. Brew scaffolds the automation with BILLING_ISSUE pre-selected.

Common Patterns

Kind follows What You Can Send. Send transactional email (a direct response to something the person did) from a transactional-purpose domain. Marketing email needs the contact’s opt-in, and being synced from RevenueCat isn’t consent. Both means the confirmation is transactional and the follow-up is marketing. No email means the automation only syncs the contact and sends nothing.

Personalization

These resolve as merge tags in the email body, subject line, and preview text. Use a fallback wherever an empty value would read badly, like {{ firstName | there }}. The trigger. prefix reads the same field, so {{ trigger.firstName }} and {{ firstName }} resolve alike; see Namespaces.

Troubleshooting

Open the canvas and confirm at least one automation bound to this event is set to Live (not Draft). The Brew integration’s Manage → Recent events panel confirms the webhook is arriving. If it isn’t there, the issue is upstream (signing-secret mismatch, RevenueCat plan tier).If the event is there but no email sent, the automation may be unpublished, or the contact unsubscribed or suppressed. From an agent, check_trigger lists what blocks the trigger, and list_trigger_events shows each event’s match state and its runs.
RevenueCat doesn’t carry user emails by default. Set the $email subscriber attribute in your app’s RevenueCat SDK after sign-in. The call differs by platform: see the note under Setup.Brew uses that attribute as the recipient on every event for that subscriber.
The HMAC signature on the webhook doesn’t verify against the signing secret stored in Brew. Usually the secret was re-generated in RevenueCat without reconnecting Brew, or the webhook was set up without HMAC signing. Re-generate the signing secret in RevenueCat and reconnect Brew with the new value.
CANCELLATION only signals intent: RevenueCat doesn’t revoke access yet. Drip a win-back email on CANCELLATION and only revoke features on the matching EXPIRATION event.
Webhooks are part of RevenueCat’s Pro plan. A project on an older legacy plan won’t deliver webhooks even if the configuration looks correct. Move it to Pro, then check that the configuration’s environment and app match the purchases you’re testing.

From an Agent or Code

Connecting RevenueCat and pasting the HMAC signing secret are app-only. From an agent or code, the rest is readable and buildable:
  • list_integrations or GET /v1/integrations confirms RevenueCat is connected to the brand.
  • check_trigger or GET /v1/automations/triggers/{triggerEventId}/readiness shows whether Brew has received an event and which Live automations consume it.
  • list_trigger_events lists recent deliveries, their match state, and the runs they started.
  • save_automation or POST /v1/automations builds an automation on any event above, and test_automation runs it to one address.
RevenueCat fires the events, so fire_trigger_event isn’t used here.

Requirements

  • A RevenueCat account on the Pro plan (free up to $2,500 in monthly tracked revenue). Legacy plans without webhooks need to move to Pro.
  • Permission to create webhook configurations in the RevenueCat dashboard.

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

Search Documentation

Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.

Ask ChatGPT or Claude

Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.