Actions44
- User Actions
- Database Actions
- Collection Actions
- Document Actions
- Index Actions
- Function Actions
- Storage Actions
Overview
This node integrates with the Appwrite API to manage databases within an Appwrite project. Specifically, for the Database - Create operation, it allows users to create a new database by specifying a unique database ID and a name. This is useful in scenarios where you want to programmatically set up new databases as part of your workflow automation, such as initializing environments, setting up multi-tenant applications, or dynamically managing data storage.
Practical example:
You might use this node to create a new database when onboarding a new client in your SaaS platform, automatically generating a dedicated database for their data isolation.
Properties
| Name | Meaning |
|---|---|
| Database ID | The unique identifier for the database. You can provide a custom string or use "unique()" to auto-generate an ID during creation. |
| Name | The display name of the database being created. |
Output
The node outputs a JSON object representing the newly created database. This typically includes details such as the database ID, name, creation timestamps, and other metadata returned by the Appwrite API.
If the operation succeeds, the output will contain the full database object as returned by the Appwrite service.
Dependencies
- Requires an API key credential for authenticating with the Appwrite API.
- The node depends on the Appwrite SDK client configured with these credentials.
- Proper network access to the Appwrite server endpoint is necessary.
Troubleshooting
Common issues:
- Providing a non-unique
databaseIdmay cause conflicts or errors. - Missing or invalid API credentials will result in authentication failures.
- Network connectivity problems to the Appwrite server will cause request timeouts or errors.
- Providing a non-unique
Error messages:
- Errors from the Appwrite API are caught and returned with detailed messages.
- If the node fails due to an API error, the message will include the reason (e.g., "Database ID already exists").
- To resolve, verify that the
databaseIdis unique, credentials are correct, and the Appwrite server is reachable.