Skip to main content
Connect RevenueCat so in-app purchase and subscription events start Brew automations. One connection covers every store RevenueCat handles, such as the App Store, Google Play, Stripe, and Web Billing. It does two things:
  • Events. Purchases, renewals, cancellations, and billing issues start automations.
  • Contacts. Each event adds or updates the subscriber in your audience, with revenuecat fields you can filter on.
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 Connects

RevenueCat sends its webhooks to a URL Brew gives you. You turn on HMAC signing in RevenueCat and give Brew the signing secret. Brew checks the signature on every delivery and rejects the ones that don’t match. The RevenueCat page in Brew has three tabs:
  • Overview sums up the connection.
  • Events lists the events, Recent events, and the Webhook URL.
  • Settings shows the last four characters of your signing secret.

Requirements

  • A RevenueCat project on a plan with webhooks. Webhooks are part of RevenueCat’s Pro plan, which is free up to $2,500 in monthly tracked revenue.
  • Permission to create webhook configurations in the RevenueCat dashboard.
  • The $email subscriber attribute set in your app. See Set the Email.

Setup

1

Copy the webhook URL from Brew

In Brew, open Integrations and click the RevenueCat card. It reads Not connected. Click Connect RevenueCat, then copy the webhook URL Brew shows.
2

Add the webhook in RevenueCat

Open app.revenuecat.com and select your project. Go to Integrations → Webhooks and click Add new configuration. Then set:
  • Name: any label, such as “Brew”
  • Webhook URL: the Brew URL
  • 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 turn on HMAC webhook signing. RevenueCat shows the signing secret once, so copy it before closing the dialog.
3

Give Brew the signing secret

Paste the signing secret into Brew and connect. The page reads Waiting for the first event.
4

Send a test event

In RevenueCat, send a test event from the webhook configuration. Brew then reads Connected. The test confirms the connection only: Brew doesn’t store it or start an automation.

Set the Email

RevenueCat doesn’t include the user’s email on its events by default. Set the $email subscriber attribute right after sign-in, before the purchase. Brew sends to that 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 })

Events

Brew supports 11 RevenueCat events, and adds a trigger for each one when you connect: The Events tab shows each event’s status. Not received yet means it has a trigger and no delivery so far. No trigger means Brew couldn’t add one, most often because your brand is at its limit of 100 triggers. Delete triggers you no longer use, then click Re-provision. Recent events lists each delivery with its state, such as fired or rejected, and signature ok when the signature matched. An event sends email only when a Live automation uses it.
CANCELLATION doesn’t revoke access. It only signals intent. Use it for a win-back during the grace period, and wait for EXPIRATION before turning off features.

What an Event Carries

Purchase and renewal events carry these fields: Other events can carry more. Check the trigger’s payload contract for the exact fields. Use them as merge tags, with a fallback for anything that can be blank.

Contacts

Each event adds or updates the subscriber in your audience by email. The contact gets revenuecat fields, such as:
  • revenuecatSubscriptionStatus, revenuecatSubscriptionPlan, revenuecatEntitlements
  • revenuecatSubscriptionStartedAt, revenuecatRenewsAt, revenuecatLastPurchaseAt
  • revenuecatStore, revenuecatEnvironment, revenuecatCountry, revenuecatCurrency
  • revenuecatPlanAmountCents, revenuecatCancelAtPeriodEnd, revenuecatAppUserId
Use them in filters and segments. A Filter on revenuecatRenewsAt reads the date the latest event saved.

Check It Works

  1. In RevenueCat, set up a sandbox webhook and use the Test Store.
  2. Publish an automation on INITIAL_PURCHASE, with a Filter that only lets your own address through.
  3. Set $email to that address, then make a sandbox purchase.
  4. On the Events tab, Recent events shows INITIAL_PURCHASE as fired. The email arrives within seconds.
Test Store subscriptions renew every few minutes, so you can test RENEWAL flows the same way.

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.

Limits

  • Triggers. The 11 events take 11 of your brand’s 100 triggers. See Trigger Limit.
  • Retention. Brew keeps each delivery for 90 days.

Reconnect or Disconnect

On the RevenueCat page’s Settings tab, the connection shows as Webhook. Click its ••• menu and choose Disconnect. Deliveries Brew already received stay, with their runs, if you connect again.

Troubleshooting

Send a test event from the webhook configuration in RevenueCat. Check that the configuration’s environment and app match where you’re testing.
Check Recent events on the Events tab. If the event is there, confirm an automation on it is Live, and that the contact isn’t unsubscribed or suppressed. If it isn’t there, check the webhook configuration and signing secret in RevenueCat.
Usually the signing secret changed in RevenueCat without updating Brew, or the webhook has no HMAC signing. Regenerate the secret in RevenueCat and reconnect Brew with the new value.
Your brand is likely at its limit of 100 triggers. Delete triggers you no longer use, then click Re-provision on the Events tab.
CANCELLATION only signals intent: RevenueCat doesn’t revoke access yet. Send the win-back on CANCELLATION and revoke features only on EXPIRATION.

From an Agent or Code

Connecting RevenueCat and pasting the signing secret are app-only. After that, an agent connected over MCP can check deliveries and build automations. Ask in plain English:
“Has Brew received an INITIAL_PURCHASE from RevenueCat, and did it start a run?”
“Build a welcome email automation on RevenueCat INITIAL_PURCHASE and test it to my address.”
From code, GET /v1/automations/trigger-instances lists each delivery, its state, and the runs it started. POST /v1/automations builds an automation on any RevenueCat trigger. RevenueCat fires the events, so you don’t send them yourself.

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.