Actions31
- Tabelle Actions
- View Actions
- Spalte Actions
- Share Actions
- Import Actions
- Zeile Actions
Overview
This node integrates with Nextcloud Tables to manage and retrieve rows from tables or views in a Nextcloud instance. Specifically, the "Alle Zeilen Abrufen (KI-Friendly)" operation under the "Zeile" (Row) resource fetches multiple rows in an AI-friendly manner, allowing advanced querying capabilities such as pagination, filtering, sorting, and searching.
Typical use cases include:
- Extracting large datasets from Nextcloud Tables for further processing or analysis.
- Retrieving filtered and sorted data subsets based on specific criteria.
- Implementing paginated data retrieval to handle large tables efficiently.
- Searching within specified columns to find relevant rows quickly.
For example, you might use this node to pull all customer records from a table, filter them by region, sort by last purchase date descending, and paginate results to process them in batches.
Properties
| Name | Meaning |
|---|---|
| Datenquelle (AI-Friendly) | Configuration of the data source to query. Choose between working with a table or a view. Depending on the choice, provide either the Table ID or View ID. |
| - Quell-Typ | Type of source: "table" for a table or "view" for a view. |
| - Tabellen-ID | The ID of the table to query (required if type is "table"). |
| - View-ID | The ID of the view to query (required if type is "view"). |
| Abfrage-Optionen (AI-Friendly) | Advanced query options for retrieving rows. Includes pagination, filters, sorting, and search configuration. |
| - Pagination | Settings to control the number of rows returned and offset for skipping rows. |
| -- Limit | Maximum number of rows to return. Default is 50. |
| -- Offset | Number of rows to skip before starting to return results. Default is 0. |
| - Filter | One or more filter rules to restrict which rows are returned. Each filter includes: |
| -- Spalten-ID | Column ID to apply the filter on. |
| -- Operator | Filter operator, e.g., equals, not equals, greater than, less than, contains, starts with, ends with, is empty, is not empty. |
| -- Wert | Value to compare against in the filter. |
| - Sortierung | One or more sorting rules to order the returned rows. Each rule includes: |
| -- Spalten-ID | Column ID to sort by. |
| -- Richtung | Direction of sorting: ascending (ASC) or descending (DESC). |
| - Suche | Search settings to perform text search across specified columns. |
| -- Suchbegriff | The search term to look for. |
| -- Spalten-IDs für Suche | Comma-separated list of column IDs to limit the search to; empty means search all columns. |
| -- Groß-/Kleinschreibung beachten | Whether the search should be case sensitive (true or false). |
Output
The node outputs an array of JSON objects representing the rows retrieved from the specified table or view. Each item corresponds to one row, containing its data fields as key-value pairs.
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 only.
Dependencies
- Requires connection to a Nextcloud instance with the Nextcloud Tables app enabled.
- Needs an API authentication token or API key credential configured in n8n to access the Nextcloud Tables API.
- No additional external services are required beyond the Nextcloud Tables API.
Troubleshooting
Common Issues:
- Incorrect Table ID or View ID: Ensure the IDs provided correspond to existing tables or views in your Nextcloud instance.
- Insufficient permissions: The API token must have rights to read the specified tables or views.
- Invalid filter or sort column IDs: Use valid column IDs that exist in the selected table/view.
- Pagination parameters out of range: Limit and offset should be non-negative integers; large offsets may cause performance issues.
Error Messages:
"Unknown resource": Indicates the resource parameter is invalid or unsupported.- API errors related to authentication or authorization: Check credentials and permissions.
- Validation errors on input properties: Verify that required fields like Table ID or View ID are set correctly depending on the source type.
To resolve errors, verify all input parameters, ensure proper API credentials, and confirm the existence and accessibility of the targeted tables/views.