🔌 Integrations

Integrations is where you supply credentials for services outside Adalo.

It is not a list of features to switch on. Your app already includes maps, files, sheets and the rest, and Ada uses them freely. The only thing it cannot do for you is hold your accounts with other companies, so this panel asks for keys and nothing else.

Status

Every service shows one of three states:

• Connected — everything required is present.
• Action needed — your app’s code uses this service but it has not been set up. A native build will fail or the feature will not work.
• Not set up — unused, and nothing to do.

When any service needs attention, the Integrations icon in the left rail is flagged, so you see it before opening the panel.

Key fields are masked like a password, with a control to reveal them.

Sign-in & Social Login

• Google Sign-In — Web client ID, iOS client ID.
• Apple Sign-In — Service ID and Redirect URL for web and Android.

Analytics & Notifications

Analytics and push notifications both come from one Firebase project, so they share a section.

• Firebase (Analytics & Notifications) — upload google-services.json for Android and GoogleService-Info.plist for iOS, plus a service account file for the backend push credential. The API key, project ID, messaging sender ID, web app ID and GA4 measurement ID can be set individually.
• Meta (Facebook) — Pixel ID for web, App ID and client token for native.

Maps & Location

• Google Maps — the Google Maps API key.

Warning

A map with no key is the common cause of a failed native build. This is exactly the case the Action needed flag exists for.

Payments

• Stripe — the publishable key.

This section also offers connecting Stripe through Stripe’s own authorization flow rather than pasting keys, and appears even when no payment service is detected in your app.

Monitoring

• Sentry — the DSN, for error reporting.

Permissions

The last section is not about keys.

Your app uses certain device features — camera, location, photos — and both app stores make the app ask the user’s permission before using them. Apple additionally requires a written reason, shown in the prompt.

These are detected automatically from what Ada actually built, so the list reflects your app rather than a fixed catalogue.

Each permission shows:

• Its name.
• A using default flag when you have not written your own reason.
• A text box for the message shown in the iOS prompt.
• The underlying iOS key, for reference.
• A Save button, active only when you have changed the text.

Note

A permission message is baked into the binary. After saving, the panel says the change takes effect on the next app build — it does not go out as an over-the-air update.

Write the reason as the user will read it, in the moment they are asked. “So you can add a photo to your profile” is a reason. “This app requires camera access” is not.