---
topic: own-database
connector: "Not yet: use the HTTP calls with the app's token"
api: "POST https://ship.embarko.ai/api/apps/{app-name}/integrations, then viaSocket"
needs_human: "Nothing, once the workspace has pay as you use on."
requires: [claim, integrations]
---

[← Guide home](https://embarko.ai/docs)

# Use your own database from an app

**On this page:** Over HTTP, Limits, What to tell the person

> Plain words unless the person is a developer. Never invent a link, name or code. [Rules](https://embarko.ai/docs/prerequisites) Needs first: [claim](https://embarko.ai/docs/claim) (over HTTP only), [integrations](https://embarko.ai/docs/integrations).

The app reads and writes a database the team already runs (MongoDB, MySQL, PostgreSQL and others) through viaSocket, which holds the connection, so the database password never goes in the app. For records that only this app keeps, use the app's own database instead (see data). It runs on viaSocket. To the person, name the outcome, not viaSocket.

**Connector:** Not yet: use the HTTP calls with the app's token

**Done when:** Every call was tested once, and the person was told what the app can now do.

**Over HTTP**

1. Turn Integrations on for the app, as the integrations topic says. If it is already on, the reply says alreadyEnabled: true; go on.
2. Download https://flow.viasocket.com/documentation/skill.md and read it whole. It is viaSocket's own guide, always current; never work from memory of it.
3. For the team's own database, as a workflow the app's code calls: open https://viasocket.com/docs/skill/my-automations.md and follow it whole.
4. For each user's own database, connected by them: open https://viasocket.com/docs/skill/app-integrations.md and follow it whole.
5. Where viaSocket reads VIASOCKET_ORG_ID, VIASOCKET_PROJECT_ID and VIASOCKET_EMBED_SECRET, use INTEGRATIONS_ORG_ID, INTEGRATIONS_PROJECT_ID and INTEGRATIONS_SECRET, in that order. Embarko set them: never ask the person for them, never hardcode them, never send the secret to the browser.
6. Test every call once, then tell the person what their app can now do, in one or two plain sentences.

**Limits**

- The workspace switch comes first: an Owner turns pay as you use on, once, on the Capabilities page. Until then turning Integrations on answers 409 integrations_disabled_for_workspace, and Embarko emails the Owners (see integrations).
- Static sites cannot use it: nothing runs that could read the keys.
- Needs a kept app: a temporary one has no workspace.

Turning Integrations on has its own errors: see the integrations topic.

**What to tell the person**

- offer: "I can connect your app to your existing database, without putting its password in the app."
- done: "Done: your app reads your database now. Its password stays out of the app."

**Next:** Turn Integrations on, then read https://flow.viasocket.com/documentation/skill.md and https://viasocket.com/docs/skill/my-automations.md.

**Related:** [integrations](https://embarko.ai/docs/integrations) · [data](https://embarko.ai/docs/data)

---

[Guide home](https://embarko.ai/docs) · JSON: add .json