Actions80
- 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
- Todos Actions
Overview
This node operation updates a specific column within a card table in a project management or organizational tool that uses the concept of "buckets" and "columns" to organize data. It allows users to modify the title and description of an existing column identified by its unique IDs.
Common scenarios include:
- Renaming a column to better reflect its purpose.
- Adding or updating a description to provide more context about the column's content.
- Adjusting metadata of columns dynamically as project requirements evolve.
Practical example:
- A user wants to update the title of a column from "In Progress" to "Ongoing Tasks" and add a description explaining what kind of tasks should be placed there.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (container) where the column exists. |
| Column Id | The numeric identifier of the column to update. |
| Title | The new title for the column. If provided, this will replace the current column title. |
| Description | The new description for the column. If provided, this will replace the current description. |
Output
The node outputs JSON data representing the updated column object after the operation completes successfully. This typically includes the updated properties such as the column's ID, title, description, and possibly other metadata returned by the API.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the external service managing the card tables.
- The base URL for API requests is constructed dynamically using credentials (e.g., a basecampId), so proper credential configuration is necessary.
- The node depends on an OpenAPI specification internally to build request properties and handle communication with the external API.
Troubleshooting
- Missing or incorrect Bucket Id or Column Id: The node requires valid numeric IDs for both bucket and column. Providing invalid or non-existent IDs will result in errors such as "Not Found" or "Invalid Identifier".
- Authentication errors: If the API key or OAuth token is missing, expired, or invalid, the node will fail with authentication errors. Ensure credentials are correctly set up and have sufficient permissions.
- Empty title or description: While these fields are optional, sending empty strings might overwrite existing values unintentionally. Confirm input values before execution.
- API rate limits or connectivity issues: Network problems or hitting API rate limits can cause failures. Check network connectivity and API usage quotas.
Links and References
- Refer to the official API documentation of the card table service for detailed information on column update endpoints.
- n8n documentation on how to configure credentials and use HTTP Request nodes may help understand underlying mechanisms.