Integrations

Integrations adds a tool to your GitHub project and keeps public keys in the CapWrap vault.

What Install does

1. CapWrap opens a pull request with the tool (and empty names in .env.example when keys are needed).
2. You merge that pull request from CapWrap (or on GitHub).
3. You copy a setup message and paste it into Lovable, Cursor, Base44, or another coding tool so it can connect the tool to your screens.

CapWrap cannot finish that last part from here. Your AI still has to wire the new tool into the app.

Keys

Some tools need a public key (RevenueCat, OneSignal, Intercom, Sentry, Firebase, PostHog, Mixpanel, Amplitude, AdMob). You paste it before Install. CapWrap stores it with your other app secrets. It is not committed to GitHub.

If you already filled a key in Settings → Environment, you can leave the field blank.

In-app review does not need a key.

After it is added

Manage integration reopens the same flow: merge if the pull request is still open, or the setup message if it is already merged.

Adding a native plugin (purchases, push, chat, ads, crash reporting, reviews) means the next store build should be a full TestFlight / Play upload, not a live update.

CapWrap does not replace RevenueCat, AdMob, Sentry, Intercom, or Firebase. Those dashboards stay the source of truth.