QuotiDatabases icon

QuotiDatabases

Allows CRUD operations at Quoti tables
Join our community

Actions5

Overview

The QuotiDatabases node enables users to perform CRUD (Create, Read, Update, Delete) operations on tables hosted in the Quoti platform. It is designed to interact with Quoti's API to manage database rows efficiently.

Common scenarios where this node is beneficial include:

  • Automating data management workflows by creating or updating records in Quoti tables.
  • Retrieving specific rows or listing multiple rows from a Quoti table for reporting or further processing.
  • Deleting obsolete or unwanted rows programmatically.
  • Integrating Quoti databases with other systems via n8n automation.

For example, you could use this node to automatically add new customer information into a Quoti table when a form is submitted, update existing entries based on external triggers, or clean up old data by deleting rows matching certain criteria.

Properties

Name Meaning
Database Name or ID The target Quoti table to operate on. You can select from a list of available databases or specify an ID directly. This corresponds to the database page URL or its ID.
Operation The action to perform on the selected table. Options are: Create, Delete, Get, List, and Update.
ID Unique identifier of the row/resource to act upon. Required for Get, Update, and Delete operations.
Properties For Create and Update operations, a collection of key-value pairs specifying the properties and their values to set on the row.
Filter For the List operation, allows filtering rows by specifying property name 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 each row returned as a separate item (false).
Limit Maximum number of rows to return in the List operation.
Options Additional optional parameters including:
- User Token: Override the default token with a user token starting with Bearer or a service account token starting with BearerStatic.
- Organization Slug: Override the organization slug.
- Organization API Key: Override the API key.
- Body: JSON body to override properties.
- Filter: JSON filter to override filters.

Output

The node outputs JSON data representing the result of the performed operation:

  • Create: Returns { success: true, id: <newly created row ID> }.
  • Get: Returns the full JSON object of the requested row.
  • List: Returns either a single item containing all rows under results (if aggregation enabled), or multiple items each representing one row.
  • Update: Returns { success: true } indicating the update was successful.
  • Delete: Returns { success: true } indicating the deletion was successful.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token (user token or service account token) to access the Quoti API.
  • Needs valid credentials configured in n8n that provide the organization slug and API tokens.
  • Uses the Quoti REST API endpoints at https://api.quoti.cloud/api/v1/.
  • Relies on HTTP requests made via Axios and query string serialization via qs.

Troubleshooting

  • Authentication Errors (401 Unauthorized):
    If the node returns an error indicating unauthorized access, verify that the provided token is correct and has the necessary permissions. Ensure the token starts with Bearer for user tokens or BearerStatic for service account tokens. Also check if the organization slug and API key are correctly set or overridden.

  • Missing Credentials:
    The node throws an error if no credentials are found. Make sure the required API credentials are properly configured in n8n before running the node.

  • Invalid Resource IDs:
    For operations requiring a row ID (Get, Update, Delete), ensure the ID is accurate and exists in the specified table.

  • Malformed JSON in Body or Filter:
    When using the JSON body or filter override options, ensure the JSON syntax is valid to avoid parsing errors.

  • API Rate Limits or Network Issues:
    Temporary network failures or rate limiting by the Quoti API may cause request failures. Retrying after some time or checking network connectivity can help.

Links and References

Discussion