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 properties such as the title and description of a column, enabling dynamic customization of the card table structure.
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 column metadata 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 within the specified bucket. |
| Title | The new title for the column. This is a string value representing the column's name. |
| Description | The new description for the column. This is a string providing additional details about the column. |
Output
The node outputs JSON data representing the updated column object after the operation completes successfully. This typically includes the updated fields such as the column's ID, title, description, and possibly other metadata returned by the API.
If the node supports binary data output, it would generally relate to attachments or files associated with the column, but based on the provided code and properties, this operation focuses solely on JSON data updates.
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 dynamically constructed using credentials (e.g., a basecampId or similar identifier).
- The node depends on an OpenAPI specification bundled internally to define request parameters and endpoints.
Troubleshooting
- Missing or incorrect Bucket Id or Column Id: The operation will fail if these identifiers are not provided or invalid. Ensure they correspond to existing resources.
- Authentication errors: If the API key or OAuth token is missing, expired, or invalid, the node will return authentication errors. Verify credentials in n8n settings.
- Invalid input values: Providing empty strings or unsupported characters in the title or description might cause API validation errors.
- Network issues: Connectivity problems can lead to timeouts or failed requests. Check network access and API availability.
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 API credentials and use HTTP request nodes for custom integrations.