Integrations

Integrations adds a tool or Capacitor plugin to your GitHub project and keeps public keys in the CapWrapp vault.

Filter the list with All integrations, Services (RevenueCat, AdMob, analytics, and similar), or Native plugins (Capacitor APIs such as geolocation, haptics, share). Search matches names and descriptions as you type.

What Install does

1. CapWrapp opens a pull request with the tool (and empty names in .env.example when keys are needed).
2. You merge that pull request from CapWrapp (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.

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

Keys

Some services need a public key (RevenueCat, OneSignal, Intercom, Sentry, Firebase, PostHog, Mixpanel, Amplitude, AdMob). You paste it before Install. CapWrapp 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.

Most native Capacitor plugins (in-app review, geolocation, haptics, in-app browser, local notifications, network, preferences, share) do 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, or a Capacitor plugin) means the next store build should be a full TestFlight / Play upload, not a live update.

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