Connect any external service to your app

1. Ask in the chat

Describe what you want (“send an SMS when an order ships”, “show the weather”), naming the service if you have one in mind. The assistant writes the code and declares the keys that code needs.

Online payment (bank card and mobile money) is provided by Makasi: in Manage › Integrations, click “Add to my app” under the payment method you want, and the assistant connects it to your app.

The key fields then appear in Manage › Integrations, grouped by service.

2. Paste your keys

1. Open Manage › Integrations. Each service has its row, “To connect” or “Connected”.
2. Click the row: each key comes with “Where to find it:” and, when one exists, a link to our guide for that service.
3. Paste the value, then save. Required and optional keys are marked as such.

3. Good to know about your keys

Your keys are encrypted and never shown again; “Replace” changes a value. A key is applied to your app at its next start. On a published app, saving a value updates the live app immediately: Makasi asks you to confirm first.

Never paste a key into the chat: the chat is kept, and a message cannot be deleted. If it happens, the assistant points you to the panel: create a new key at the provider, revoke the old one, and paste the new one in Manage › Integrations.

“Add a key” lets you add a key by hand.

4. Who sees your keys

The assistant never receives the values through Makasi: it only knows the names of the keys. Once your app runs, the code it wrote uses those values — that is what they are for.

In your app’s logs, key values are masked. It is a precaution, not a guarantee: it relies on the code not printing them.

5. The callback address

Some services need to reach your app themselves — to confirm a payment, for example. The service’s window then shows the address to copy (“Copy this address into …”), with a “Copy” button.

This address never changes: set it up at the provider right away. It starts answering once your app is published, and it stays the same if you add a domain.

For a provider to reach your app at any time, the app must be published on a paid plan: on the free plan, a published app goes to sleep when inactive.

6. Test first, then production

Start with the provider’s test keys. When everything works, replace them with the production keys in Manage › Integrations. Before each publication, Makasi asks you to check that your keys are production values.

For mobile money (pawaPay), the service’s window shows a “Mode” setting: Test or Production. Switching to production means choosing Production there, along with the production keys: no code change.

Another service with two addresses — one for tests, one for production — gets one more key, named after the service and ending in _BASE_URL, with both addresses in its hint. Switching to production means changing that value along with the keys.

7. A service the assistant doesn’t know

The assistant does not guess an API. It reads our documentation, then the provider’s official documentation.

If it cannot find reliable information, it delivers no guessed call: the feature stays disabled and answers with a clear “not configured” error — never a fake success — and the build summary tells you so, with the links it read. You can then give it the right documentation link and ask again.

8. Examples

Our guides cover a few common services in detail. They are examples: any service with an API can be connected the same way.

9. What it costs

Storing your keys is free on every plan. Building the integration is paid in credits, like any build.

Server code runs on paid plans only. A feature whose secret key is used by your app’s own server code — payments, SMS, an AI service… — therefore needs a paid plan. Sign-in with Google, GitHub or another provider is the exception: its secret key is read by your app’s built-in sign-in, with no server code, and it works on the free plan. On the free plan, the assistant tells you before spending more, and can offer a version that works without a secret key.