QuotiDatabases icon

QuotiDatabases

Allows CRUD operations at Quoti tables

Actions5

Overview

This n8n node allows you to retrieve a single row (record) from a specified Quoti database table by its unique ID. It is designed for the "Default" resource and the "Get" operation, meaning it fetches detailed information about one specific entry in a Quoti-managed table.

Common scenarios:

  • Fetching user or record details for further processing in an automation workflow.
  • Looking up a specific item by its ID to enrich data or trigger conditional logic.
  • Integrating Quoti database records with other systems via n8n.

Practical example:
You have a workflow that receives a record ID from a webhook or another system, and you want to pull all details of that record from your Quoti database for reporting, notification, or further processing.

Properties

Name Type Meaning
Database Name or ID options The identifier or name of the Quoti database table. You can select from a list or enter the ID directly (from Notion's 'copy link' or just the ID).
ID string The unique identifier of the row (record) you want to retrieve from the selected database table.
Options collection Additional optional settings:
- User Token (string): Override the default token for authentication.
- Organization Slug (string): Override the organization slug.
- Organization API Key (string): Override the API key.
- Body (json): Not used for "Get" operation.

Output

  • The output will be a single JSON object representing the retrieved row from the Quoti database.
  • All fields present in the original record are included as key-value pairs in the json property of the output item.
  • If an error occurs (e.g., invalid credentials), the output will contain an error field with details.

Example output:

{
  "json": {
    "id": "12345",
    "name": "John Doe",
    "email": "john@example.com",
    "...": "..."
  },
  "pairedItem": {
    "item": 0
  }
}

Error output example:

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

Dependencies

  • External Service: Requires access to the Quoti API (https://api.minhafaculdade.app/api/v1/).
  • API Credentials: Needs valid Quoti API credentials (API key and organization slug) configured in n8n credentials under quotiApi.
  • Optional: User Token and Organization Slug/API Key can be overridden per request using the "Options" property.

Troubleshooting

Common issues:

  • Invalid or missing credentials: If the API key or organization slug is incorrect or missing, the node will throw an error.
  • Authentication errors: If the provided token is invalid or expired, you'll receive an error message indicating authentication failure.
  • Incorrect Database Name or ID: If the table does not exist or the ID is wrong, the node may return an empty result or an error.

Common error messages:

  • "No credentials got returned!" — Make sure your n8n credentials for Quoti are set up correctly.
  • "The user could not be retrieved. There is a problem with the user's token or the api key." — Check your API key and token; ensure they are valid and not expired.
  • "Unknown error: ..." — Review the error message for more details; it may indicate network issues, permission problems, or malformed requests.

Links and References

Discussion