Overview
The QuotiDatabases node enables CRUD (Create, Read, Update, Delete) operations on tables within the Quoti platform, which appears to be a database or form management service. This node is useful for automating workflows that require interaction with Quoti tables, such as synchronizing data between Quoti and other systems, batch updating records, or extracting information for reporting.
Common scenarios:
- Creating new entries in a Quoti table from incoming workflow data.
- Listing or retrieving specific rows for further processing.
- Updating or deleting records based on workflow logic.
- Integrating Quoti data with other services via n8n.
Practical examples:
- Automatically add a new student record to a Quoti table when a registration form is submitted.
- Fetch all rows from a Quoti table and send them to an email or another system.
- Update a row in Quoti when a related event occurs in another app.
Properties
| Name | Type | Meaning |
|---|---|---|
| Database Name or ID | options | The identifier or name of the Quoti table to operate on. Can be selected from a list or specified directly (from Notion's 'copy link' or just the ID). |
| Options | collection | Additional configuration options: - User Token (string): Override the default token; must start with Bearer or BearerStatic.- Organization Slug (string): Override the organization slug. - Organization API Key (string): Override the API key. - Body (json): Provide a custom JSON body to override property values. |
Output
Success output:
- For "list" operation:
- If Raw Data is true:
{ "rows": [ ... ] // Array of row objects from the table } - If Raw Data is false:
Each output item contains a single row object in itsjsonfield.
- If Raw Data is true:
- For "get" operation:
Thejsonfield contains the retrieved row object. - For "create", "update", "delete" operations:
{ "sucess": true }
- For "list" operation:
Error output:
- If authentication fails (e.g., invalid token or API key):
{ "error": { "message": "The user could not be retrieved. There is a problem with the user's token or the api key.", "type": "unauthenticated" } } - For other errors:
{ "error": { "message": "Unknown error: <error message>", "type": "unknown", "errorData": { ... } } }
- If authentication fails (e.g., invalid token or API key):
Binary data:
This node does not output binary data.
Dependencies
- External Service: Requires access to the Quoti API at
https://api.minhafaculdade.app. - API Credentials:
- Organization Slug (
orgSlug) - API Key (
apiKey) - Optionally, a User Token (
token) starting withBearerorBearerStatic
- Organization Slug (
- n8n Configuration:
- Must have a credential named
quotiApiconfigured with the required fields.
- Must have a credential named
Troubleshooting
Common issues:
Authentication errors:
- Error:
"The user could not be retrieved. There is a problem with the user's token or the api key."- Cause: Invalid or missing API key or token.
- Solution: Check your credentials and ensure the token starts with
BearerorBearerStatic.
- Error:
Invalid Table/Row IDs:
- If you provide an incorrect table name/ID or row ID, the operation may fail or return no results.
Malformed JSON Body:
- If using the "Body" option, ensure the JSON is valid. Otherwise, parsing will fail.
Missing Required Fields:
- Ensure all required properties are provided, especially "Database Name or ID".
Links and References
- n8n Expressions Documentation
- Quoti Platform (Minhafaculdade)
(Note: Official API documentation may be private or internal.)