Nextcloud Tables icon

Nextcloud Tables

Verwalten Sie Ihre Nextcloud Tables - Tabellen, Zeilen und Daten
Join our community

Actions31

Overview

The node provides functionality to update a "View" in Nextcloud Tables using an AI-friendly configuration. It allows users to modify the view's metadata such as title, emoji, and description, as well as adjust filtering and sorting rules applied to the view. This is useful for dynamically customizing how data is presented in a table view without manually editing it in the Nextcloud interface.

Typical use cases include:

  • Automatically updating views based on changing business logic or user preferences.
  • Adjusting filters and sorts programmatically to tailor data presentation for different scenarios.
  • Renaming or rebranding views with new titles or emojis to reflect updated content or context.

For example, you might update a view to show only rows where a status column equals "Open" and sort them by priority descending, while also changing the view’s title to "Open Tasks 🔥".

Properties

Name Meaning
Update-Konfiguration (AI-Friendly) Configuration for updating the view's basic properties:
• View-ID: The identifier of the view to update.
• Neuer Titel: New title for the view (leave empty to keep unchanged).
• Neues Emoji: New emoji for the view (leave empty to keep unchanged).
• Neue Beschreibung: New description text (leave empty to keep unchanged).
Filter-Konfiguration (AI-Friendly) Defines filter rules for the view. Each rule consists of one or more filters:
• Spalten-ID: Column ID to apply the filter on.
• Operator: Comparison operator, options are EQ (equals), NEQ (not equals), GT (greater than), GTE (greater or equal), LT (less than), LTE (less or equal), LIKE (contains).
• Wert: Value to compare against.
Sortierungs-Konfiguration (AI-Friendly) Defines sorting rules for the view. Each rule consists of one or more sorting criteria:
• Spalten-ID: Column ID to sort by.
• Richtung: Direction of sorting, either ASC (ascending) or DESC (descending).

Output

The node outputs JSON data representing the result of the update operation on the view. This typically includes confirmation details or the updated view object returned from the API. The exact structure depends on the underlying API response but generally confirms success and may include updated view metadata.

No binary data output is involved.

Dependencies

  • Requires an active connection to a Nextcloud instance with the Tables app installed.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node relies on internal handlers for views to perform the update operation via Nextcloud Tables API.

Troubleshooting

  • Common issues:

    • Invalid or missing View-ID will cause the update to fail.
    • Providing invalid column IDs in filter or sort configurations can lead to errors.
    • Incorrect operator values or unsupported operators in filters may cause request rejection.
    • Network or authentication failures if API credentials are misconfigured.

  • Error messages:

    • "Unknown resource" error indicates the resource parameter was not set to "view".
    • API errors related to permissions or invalid parameters will be surfaced; ensure the API token has sufficient rights.
    • If the node throws errors about malformed filter or sort rules, verify that all required fields (columnId, operator/direction, value) are correctly provided.

  • Resolution tips:

    • Double-check the View-ID and column IDs exist in your Nextcloud Tables environment.
    • Validate filter operators and sort directions against allowed values.
    • Ensure API credentials are valid and have necessary scopes.
    • Use the node’s continue-on-fail option to handle partial failures gracefully.

Links and References

Discussion