QuotiDatabases icon

QuotiDatabases

Allows CRUD operations at Quoti tables
Join our community

Actions5

Overview

The node "QuotiDatabases" enables CRUD (Create, Read, Update, Delete) operations on tables within the Quoti platform. It is designed to interact with Quoti databases by allowing users to list entries, retrieve specific rows, create new rows, update existing rows, or delete rows from a selected database table.

This node is beneficial in scenarios where you want to automate data management tasks in Quoti without manual intervention. For example:

  • Automatically updating records in a Quoti table based on external triggers.
  • Fetching and processing data from Quoti tables for reporting or integration with other systems.
  • Creating new entries in Quoti tables from form submissions or other data sources.
  • Deleting obsolete or unwanted records programmatically.

Properties

Name Meaning
Database Name or ID The target Quoti database table to operate on. Can be selected from a list of available databases or specified via an expression. This corresponds to the database page URL or its ID.
Operation The action to perform on the selected table. Options: create, delete, get, list, update.
ID Unique identifier of the row/resource to get, update, or delete. Required for get, update, and delete operations.
Properties A collection of key-value pairs representing the properties to set when creating or updating a row. Each property can be selected from the database's available properties or specified by ID, with a corresponding value.
Filter Used only for the list operation to filter rows by a specific property and value.
Aggregate Rows In One Item For the list operation, determines whether all rows should be aggregated into a single output item (true) or if each row should be output as a separate item (false).
Limit Maximum number of results to return for the list operation.
Options Additional optional parameters including:
- User Token: Overrides the default token used for authentication.
- Organization Slug: Overrides the organization slug.
- Organization API Key: Overrides the API key.
- Body: JSON body that overrides the defined properties.
- Filter: JSON filter that overrides the defined filters.

Output

The node outputs JSON data structured according to the operation performed:

  • Get: Outputs a single item with the JSON data of the requested row.
  • List: Outputs either a single item containing an array of all rows (if aggregation enabled) or multiple items each representing one row.
  • Create: Outputs a success confirmation and the ID of the newly created row.
  • Update: Outputs a success confirmation.
  • Delete: Outputs a success confirmation.

If an error occurs during execution, the output JSON will contain an error object with a message and type describing the issue.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Quoti API service.
  • Needs valid credentials including an API key and organization slug, which can be provided via node credentials or overridden in the node options.
  • Uses Axios for HTTP requests and qs for query string serialization internally.
  • Requires proper configuration of authentication tokens (either user tokens starting with "Bearer" or service account tokens starting with "BearerStatic").

Troubleshooting

  • Authentication Errors (401 Unauthorized): Occur if the provided token or API key is invalid or missing. Ensure that the token starts with the correct prefix ("Bearer" or "BearerStatic") and that credentials are correctly configured.
  • No Credentials Returned: If the node cannot retrieve credentials, it will throw an error. Verify that the credentials are properly set up in n8n.
  • Invalid Resource IDs: Providing incorrect or non-existent row IDs for get, update, or delete operations will result in errors. Double-check the IDs.
  • Malformed JSON in Body or Filter: When using the JSON override fields, ensure the JSON syntax is correct to avoid parsing errors.
  • API Rate Limits or Network Issues: May cause request failures; check network connectivity and API usage limits.

Links and References

Discussion