QuotiDatabases icon

QuotiDatabases

Allows CRUD operations at Quoti tables

Actions5

Overview

The QuotiDatabases node allows you to perform CRUD (Create, Read, Update, Delete) operations on tables within the Quoti platform. Specifically, the Update operation enables you to modify existing records in a selected database table by specifying the record's ID and the properties you wish to update.

Common scenarios:

  • Automating updates to student or resource records in an educational management system.
  • Integrating with other n8n workflows to keep data synchronized between Quoti and external systems.
  • Bulk updating records based on triggers from other applications.

Practical example:
Suppose you have a workflow that receives updated user information from another system. You can use this node to update the corresponding user's record in your Quoti database automatically.

Properties

Name Type Meaning
Database Name or ID options The target database table in Quoti. Select from a list or provide the ID/URL directly. Required for identifying which table to update.
ID string Unique identifier of the record (row) you want to update. This is required for the update operation.
Properties fixedCollection Key-value pairs representing the fields to update. Each property includes a "Name or ID" (the field name) and a "Value" (the new value to set).
Options > User Token string Optional. Overrides the default authentication token. Must start with Bearer or BearerStatic.
Options > Organization Slug string Optional. Overrides the organization slug from credentials.
Options > Organization API Key string Optional. Overrides the API key from credentials.
Options > Body json Optional. If provided, this JSON body will override the Properties defined above. Useful for advanced or bulk updates.

Output

  • On success, the output will be:

    {
  "sucess": true
}
    • The output item will be paired with the input item index.

  • On error, the output will include an error object:

    {
  "error": {
    "message": "The user could not be retrieved. There is a problem with the user's token or the api key.",
    "type": "unauthenticated"
  }
}

    or

    {
  "error": {
    "message": "Unknown error: <error message>",
    "type": "unknown",
    "errorData": { ... }
  }
}

  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the Quoti API.
  • API Credentials: Needs valid Quoti API credentials (orgSlug, apiKey). These are typically configured in n8n credentials but can be overridden per node execution via the Options property.
  • User Token: For some operations, a Bearer or BearerStatic token may be required.
  • n8n Configuration: Ensure the quotiApi credential is set up in your n8n instance.

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, missing, or expired token/API key.
      • Solution: Check your credentials and ensure the token starts with Bearer or BearerStatic.

  • Invalid Input Data:

    • Error: "Unknown error: <error message>"
      • Cause: Malformed JSON in the Body, missing required fields, or invalid property names.
      • Solution: Double-check the Properties and Body fields for correct formatting and required values.

  • Missing Record ID:

    • If the "ID" property is empty, the update cannot proceed.
      • Solution: Ensure you provide the correct record ID.

  • Overriding Properties:

    • If both Properties and Body are provided, the Body will take precedence and override Properties.

Links and References

Discussion