Connect services to your app
Add accounts, saved data, AI responses, generated images and voice. Choose a service, connect it to your app and verify the feature in a native preview.
Connect the service your feature needs, then test what your users will actually do. A saved connection is the starting point; a working sign-in, answer, illustration or voice is the result.
You can ask for a feature in Studio and use the connection request in the conversation, or open the connection controls yourself.
On this page
Choose by what your app needs
| Service | Start with | How you connect |
|---|---|---|
User accounts and shared, saved app data | Authorize your Supabase account, select a project and review database setup | |
A conversational assistant or text generation | OpenAI API key | |
Writing, explanations and reasoning with Claude | Claude API key | |
AI chat using a model available in your Groq account | Groq API key | |
An image generated from a prompt | Replicate API token | |
Spoken narration from text | ElevenLabs API key |
Describe the feature first
For example: “Generate a cover illustration for each bedtime story using Replicate.” Include where the result should appear and whether people should be able to save it.
When Studio requests a connection, use its Connect button. You can also use App options (+) → Connectors for AI and voice providers. Supabase has its own App options (+) → Supabase entry.
Example: adding product photography to Bazario. Illustrated walkthrough.
- Describe the feature you want to add.
- Read the service request, then choose Connect Replicate.
- Complete the connection form and return to the same conversation.
Check the feature, not just the badge
Finish the requested change
Return to the conversation after connecting. Let Studio add the feature, then read its result or any remaining setup request.
Try it in the native preview
Use the iOS or Android preview. Submit a short prompt, generate one image, play one narration, or save one record—whichever proves your feature works.
Reopen and try a failure
If your feature promises saved results, close and reopen the app to check them. Also test an empty input, a slow request and a recoverable failure. A successful first request does not prove persistence.
Follow the connection screens
Open App options (+), choose Connectors, then select a provider. This Replicate example shows the private token form and the saved connection. Each provider has its own logo and credential hint.
1 / 4 · App optionsThe actual App options menu above the + button. It contains separate Supabase, Connectors and App memory actions.
The actual connection screens. Empty form and illustrative saved state; no credential is shown.
- Open App options (+) → Connectors in the app you want to connect.
- Choose Replicate in the catalogue, then enter your API Token in its private form and select Save.
- Return to the conversation and test the feature. Connected means a credential is saved, not that a provider request has succeeded.
Costs and the information your app sends
Your connected provider handles its own API usage and billing. Those charges are separate from RNBlocks credits used while building your app. Review the provider’s quota and billing before testing with a large audience.
An AI feature sends the information needed for that request to its provider. Decide what your app should send, explain that clearly to your users, and test any permission and decline choices before release. Connecting a service does not automatically add a saved history, private file library or every feature in that provider’s API.
When a connection does not work
When asking Studio for help, include the action, the visible error and whether it happened on iOS or Android. Keep credentials out of the message.
| What you see | What to check |
|---|---|
Connected, but the feature fails | Confirm the key is active at the provider and that its account has access to the requested model or feature. Saving a key does not validate a provider request. |
A quota or billing error | Check the connected provider’s usage and billing. Adding RNBlocks credits does not refill a separate provider account. |
A connection works in another app | Open this app’s own Connectors panel. Each app has its own saved connection. |
A file or model is unsupported | Ask Studio to inspect the exact request. A provider offering a feature does not mean every endpoint, attachment format or stored resource is supported by the connector. |
A result disappears after reopening | Ask how the result is stored. A completed request and a saved connection do not automatically create persistent app data. |