Nextcloud Tables icon

Nextcloud Tables

Manage your Nextcloud Tables - tables, rows, and data
Join our community

Actions31

Overview

The "Get All Rows" operation in the Nextcloud Tables node allows you to retrieve multiple rows from either a table or a view within your Nextcloud Tables environment. This operation is useful when you want to fetch bulk data for processing, reporting, or integration with other systems.

Common scenarios include:

  • Extracting all records from a specific table for data analysis.
  • Retrieving filtered subsets of rows based on column values.
  • Sorting rows by one or more columns to organize data before further use.
  • Performing text searches across row data to find relevant entries quickly.
  • Paginating through large datasets by using limit and offset parameters.

For example, you might use this operation to get all customer records from a "Customers" table, filter them to only those in a certain city, sort them by last purchase date descending, and then process that data in an automation workflow.

Properties

Name Meaning
Source Choose whether to work directly with a Table (fetch rows from a table) or a View (fetch rows from a predefined view).
Table Select the target table by choosing from a list or entering its numeric ID. Required if Source is set to Table.
View Select the target view by choosing from a list or entering its numeric ID. Required if Source is set to View.
Additional Options Collection of optional settings:
- Limit Maximum number of rows to return (1 to 1000). Recommended between 50-200 for best performance.
- Offset Number of rows to skip, used for pagination (e.g., offset 50 skips first 50 rows).
- Enable Filters Boolean flag to enable filtering rows based on column values.
- Enable Sorting Boolean flag to enable sorting rows by specified columns.
- Enable Search Boolean flag to enable full-text search on text columns.
Filter When filters are enabled, define one or more filter rules specifying:
- Column The column to apply the filter on.
- Operator Comparison operator such as equals, not equals, greater than, contains, starts with, ends with, is empty, etc.
- Value The value to compare against (not required for "is empty" or "is not empty").
Sorting When sorting is enabled, define one or more sorting rules specifying:
- Column The column to sort by.
- Direction Sort direction: Ascending (A-Z, 1-9, oldest first) or Descending (Z-A, 9-1, newest first).
Search When search is enabled, configure:
- Search Term Text term to search for in text columns.
- Search Only Specific Columns Optionally restrict search to specific columns; leave empty to search all text columns.
- Case Sensitive Whether the search should be case-sensitive or not.

Output

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

If binary data is present in any row fields, it would typically be represented separately in a binary property, but this operation primarily returns JSON data representing row content.

Example output snippet (simplified):

[
  {
    "id": "123",
    "Name": "John Doe",
    "Email": "john@example.com",
    "CreatedDate": "2024-01-15T10:00:00Z"
  },
  {
    "id": "124",
    "Name": "Jane Smith",
    "Email": "jane@example.com",
    "CreatedDate": "2024-02-20T14:30:00Z"
  }
]

Dependencies

  • Requires a valid API authentication token credential configured in n8n to connect to the Nextcloud Tables API.
  • The node depends on Nextcloud Tables API endpoints for tables, views, columns, and rows.
  • Proper permissions on the Nextcloud instance to read tables and views.
  • Network connectivity to the Nextcloud server hosting the tables.

Troubleshooting

  • Invalid Table or View ID: If you enter an invalid or non-numeric ID for table or view, the node will throw a validation error. Ensure IDs are numeric and correspond to existing resources.
  • Permission Denied: If the API credentials lack permission to access the specified table or view, the node will fail. Verify API key permissions and user roles.
  • Limit Exceeded: Requesting more than 1000 rows per call is not allowed. Use pagination with limit and offset to retrieve larger datasets.
  • Filter or Sort Misconfiguration: Incorrect column selections or unsupported operators may cause errors. Make sure columns exist and operators are appropriate for the column data type.
  • Search Not Returning Results: If search is enabled but no results appear, check that the search term matches text columns and that case sensitivity is set correctly.
  • Network Issues: Connectivity problems to the Nextcloud server will cause request failures. Check network and server status.

Links and References

Discussion