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 Quoti tables, which are database-like resources managed via the Quoti API. The "List" operation specifically retrieves multiple rows from a selected Quoti table (database). It supports filtering results by properties, limiting the number of returned rows, and optionally aggregating all rows into a single output item or returning each row as a separate item.

This node is useful when you want to integrate Quoti data into your workflows, for example:

  • Fetching a list of records from a specific Quoti table to process or analyze.
  • Filtering records based on property values to narrow down results.
  • Aggregating all rows into one item for batch processing or exporting.

Properties

Name Meaning
Database Name or ID Select the target Quoti database (table) by name or ID. This identifies which table to query. You can choose from a loaded list or specify an ID via expression.
Filter Optional filter to select rows where a specified property matches a given value. You pick a property from the database's properties and provide the value to filter by.
Aggregate Rows In One Item Boolean flag indicating whether to combine all retrieved rows into a single output item (true), or return each row as a separate output item (false).
Limit Maximum number of rows to return in the response. Must be at least 1. Defaults to 25.
Options → User Token Optionally override the user token used for authentication. Must start with "Bearer" for user tokens or "BearerStatic" for service account tokens. If not set, the token from credentials or input headers is used.
Options → Organization Slug Optionally override the organization slug used in API requests. Defaults to the slug from credentials.
Options → Organization API Key Optionally override the API key used for authentication. Defaults to the key from credentials.
Options → Body JSON object that overrides the standard request body properties. Useful for advanced or custom API calls.
Options → Filter JSON object that overrides the standard filter properties. Useful for complex filtering beyond the UI options.

Output

The node outputs items containing a json field structured as follows for the "List" operation:

  • If Aggregate Rows In One Item is enabled (true):
    • json.results: An array of objects, each representing a row from the queried Quoti table.
  • If aggregation is disabled (false):
    • Each output item corresponds to a single row.
    • json: Contains the individual row data as an object.

Additionally, for other operations (not requested here), the output may include success flags or IDs.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Quoti API.
  • Needs valid credentials including:
    • An API authentication token (user token or service account token).
    • Organization slug identifying the Quoti organization.
  • The node uses Axios for HTTP requests and qs for query string serialization.
  • Credentials must be configured in n8n with appropriate permissions to access the Quoti API.

Troubleshooting

  • Authentication Errors (401 Unauthorized):

    • Error message: "The user could not be retrieved. There is a problem with the user's token or the api key."
    • Cause: Invalid, missing, or expired API token or key.
    • Resolution: Verify and update the API token or key in credentials or override options.

  • No Credentials Returned:

    • Error thrown if no credentials are found during execution.
    • Resolution: Ensure credentials are properly set up and linked to the node.

  • Filter Misconfiguration:

    • If filters do not match any rows, the output will be empty.
    • Resolution: Double-check property names and filter values; use expressions carefully.

  • Limit Too Low or High:

    • Setting limit below 1 is invalid.
    • Very high limits might cause performance issues or API rate limiting.
    • Resolution: Use reasonable limits according to expected data size.

  • Malformed JSON in Override Fields:

    • If JSON provided in "Body" or "Filter" options is invalid, the request may fail.
    • Resolution: Validate JSON syntax before input.

Links and References

Discussion