Nextcloud Tables icon

Nextcloud Tables

Manage your Nextcloud Tables - tables, rows, and data

Overview

The "Get All Rows (AI-Friendly)" operation in the Nextcloud Tables node retrieves multiple rows from a specified data source within Nextcloud Tables, either from a table or a view. This operation is designed to be flexible and powerful, allowing users to query large datasets with pagination, filtering, sorting, and search capabilities.

Typical use cases include:

  • Extracting all records from a specific table or view for reporting or further processing.
  • Applying filters to retrieve only rows matching certain criteria.
  • Sorting data to organize output according to column values.
  • Searching across columns for specific terms, useful for quick lookups or AI-driven data analysis.

For example, a user might want to fetch all customer records where the "Status" column equals "Active", sorted by "Last Purchase Date" descending, and limited to 100 rows per request.

Properties

Name Meaning
Data Source (AI-Friendly) Configuration of the data source to query. Choose between:
- Source Type: "table" or "view"
- Table ID: The identifier of the table (required if type is "table").
- View ID: The identifier of the view (required if type is "view").
Query Options (AI-Friendly) Advanced options to customize the row retrieval query:
- Pagination: Controls how many rows to return (Limit) and how many rows to skip (Offset).
- Filters: One or more filter rules specifying column IDs, operators (e.g., equals, contains, greater than), and values to filter rows.
- Sorting: One or more sorting rules specifying column IDs and direction (Ascending or Descending).
- Search: Search term configuration including the term itself, which columns to search (comma-separated IDs, empty means all), and case sensitivity flag.

Output

The node outputs an array of JSON objects representing the rows retrieved from the specified table or view. Each object corresponds to one row and contains key-value pairs where keys are column identifiers or names and values are the respective cell contents.

If binary data were involved (not indicated here), it would typically be included in a separate binary property, but this operation focuses on JSON row data.

Dependencies

  • Requires a valid API authentication token credential configured in n8n to connect to the Nextcloud Tables API.
  • The node depends on Nextcloud Tables service being accessible and properly configured.
  • No additional external services are required beyond the Nextcloud Tables API.

Troubleshooting

  • Common Issues:

    • Incorrect or missing Table ID or View ID will cause the operation to fail.
    • Using incompatible filter operators or invalid column IDs may result in errors or empty results.
    • Pagination parameters exceeding available data range may return fewer rows than expected.
    • Network or authentication issues can prevent successful API calls.
  • Error Messages:

    • "Unknown resource": Indicates an unsupported resource was selected; ensure "Row" resource is chosen.
    • API errors related to authorization or invalid IDs usually indicate misconfiguration of credentials or incorrect input parameters.
  • Resolutions:

    • Verify that the Table ID or View ID exists and is accessible with the provided credentials.
    • Double-check filter and sorting configurations for correctness.
    • Ensure the API key or authentication token is valid and has sufficient permissions.
    • Use smaller pagination limits during testing to avoid timeouts or large data loads.

Links and References

Discussion