QuotiDatabases icon

QuotiDatabases

Allows CRUD operations at Quoti tables
Join our community

Actions5

Overview

The QuotiDatabases node enables CRUD (Create, Read, Update, Delete) operations on tables within the Quoti platform. It is designed to interact with Quoti's API to manage data records in specified databases (tables). This node is useful for automating workflows that require reading from or writing to Quoti tables, such as syncing data between systems, updating records based on external triggers, or retrieving specific entries for reporting.

Typical use cases include:

  • Retrieving a single record by its unique ID.
  • Listing multiple records with optional filtering and limiting.
  • Creating new records with specified properties.
  • Updating existing records by ID.
  • Deleting records by ID.

For example, you could use this node to fetch a user's details from a Quoti table when a form is submitted, update their status, or delete obsolete entries automatically.

Properties

Name Meaning
Database Name or ID The target database (table) to operate on. You can select from a list of available databases or specify an ID directly. This corresponds to the Quoti table name or identifier.
Operation The action to perform on the selected database. Options are: Create, Delete, Get, List, Update.
ID Unique identifier of the resource (row) to get, update, or delete. Required for get, update, and delete operations.
Properties For create and update operations, a collection of property key-value pairs to set on the record. Each property is identified by name or ID and assigned a string value.
Filter For list operation, a filter specifying which records to retrieve based on property values. Only one filter property can be set at a time.
Aggregate Rows In One Item For list operation, whether to aggregate all returned rows into a single output item (true) or return each row as a separate item (false). Defaults to true.
Limit For list operation, maximum number of results to return. Minimum is 1, default is 25.
Options Additional options including:
- User Token: Override the token used for authentication; must start with Bearer or 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 data in the json field of each item:

  • For get: Outputs the retrieved record as JSON.
  • For list:
    • If aggregation is enabled, outputs a single item with a results array containing all records.
    • Otherwise, outputs one item per record.
  • For create: Outputs a success confirmation and the created record's ID.
  • For update: Outputs a success confirmation.
  • For delete: Outputs a success confirmation.

No binary data is produced by this node.

Example output for a get operation might look like:

{
  "json": {
    "id": "123",
    "name": "John Doe",
    "email": "john@example.com"
  }
}

For a list operation with aggregation:

{
  "json": {
    "results": [
      { "id": "123", "name": "John Doe" },
      { "id": "124", "name": "Jane Smith" }
    ]
  }
}

Dependencies

  • Requires valid credentials for the Quoti API, including an API key and organization slug.
  • Uses Axios for HTTP requests.
  • Requires n8n credential configuration for the Quoti API authentication.
  • Supports overriding credentials via node parameters for token, organization slug, and API key.
  • Uses query-string library for parameter serialization.

Troubleshooting

  • Authentication errors (401 Unauthorized):
    Occur if the user token or API key is invalid or missing. Ensure the token starts with Bearer for user tokens or BearerStatic for service account tokens. Verify credentials in n8n or override them correctly in node options.

  • No credentials returned error:
    Happens if the node cannot access the configured credentials. Check that the Quoti API credentials are properly set up in n8n.

  • Invalid or missing IDs:
    For get, update, and delete operations, ensure the ID property is provided and correct.

  • Malformed JSON in Body or Filter overrides:
    When using the JSON editor for Body or Filter options, ensure valid JSON syntax to avoid parsing errors.

  • API request failures:
    Network issues or incorrect organization slugs can cause request failures. Verify connectivity and correct organization slug usage.

Links and References

Discussion