Create and connect databases

Cloudgate workflows can use managed SQLite data and supported remote SQL connections. Start by choosing the database engine and the sandbox and production resources your workflows should reach.

Choose your storage#

Use a managed database for data that belongs with your Cloudgate solution. Connect a remote database when an existing system remains the source of truth or requires its own operating model.

SQL Server, PostgreSQL, MySQL, and SQLite use different SQL dialects. The query you write must match the selected connection; a working SQLite example is not automatically portable to another engine.

Set up a resource#

1. Open Workflows → Databases.
2. Create a database or configure the supported connection type.
3. Name it for its purpose and environment.
4. Test connectivity with a read-only query.
5. Create the required schema using an intentional migration or setup script.
6. Bind the Database nodes that should use it.

Use credentials with the operations your workflow actually needs. Confirm that the running Cloudgate service can reach a remote database; connectivity from your laptop alone is not sufficient.

Plan environment separation#

Use separate test data for sandbox development. Inspect each Database node's binding before executing a write. Two different API prefixes can still reach the same database if both bindings point there.

Identity-provider accounts and platform records are separate from your workflow's application database. Do not query internal platform tables as a substitute for supported identity operations.

Keep the API contract stable#

Select explicit columns and shape the public response deliberately. Add limits and filters for growing collections. Index fields used for frequent lookups, and confirm the query plan in the database's tooling when performance matters.

See SQL and parameters, the database API guide, and backup planning.