Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation updates a specific column within a card table in a project management or organizational tool. It allows users to modify the metadata of a column, such as its title and description, identified by unique bucket and column IDs. This is useful for dynamically managing and organizing data structures in workflows where card tables represent task boards, kanban-style columns, or categorized lists.
Practical examples include:
- Renaming a column to reflect a change in workflow stage.
- Adding or updating a description to clarify the purpose of a column.
- Automating column updates based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (or board) containing the column to update. |
| Column Id | Numeric identifier of the column to be updated within the specified bucket. |
| Title | New title/name for the column. |
| Description | New description text for the column, providing additional context or details. |
Output
The node outputs JSON data representing the updated column object after the API call completes successfully. This typically includes the updated properties such as the column's ID, title, description, and possibly other metadata returned by the service.
If the node supports binary data output, it would generally relate to attachments or media associated with the column, but this operation focuses on textual metadata updates only.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing card tables.
- The base URL for API requests is constructed dynamically using credentials (e.g., a workspace or account ID).
- The node depends on the external service's REST API endpoint that handles card table column updates.
Troubleshooting
- Invalid Bucket or Column Id: If the provided IDs do not exist or are incorrect, the API will likely return a "not found" error. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Empty Title or Description: While optional, sending empty strings might overwrite existing values unintentionally. Confirm input values before execution.
- API Rate Limits: Frequent updates may hit rate limits imposed by the external service. Implement retry logic or reduce request frequency if errors occur.
Links and References
- Refer to the external service’s official API documentation for card tables and column management endpoints.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.