Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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 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 or OAuth2 token configured in n8n to authenticate requests against the external service managing card tables.
- The base URL for API requests is constructed dynamically using credentials (e.g., a Basecamp account ID).
- The node depends on an OpenAPI specification file (
Basecamp.api.json) bundled internally to define available operations and parameters.
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 that the IDs correspond to existing resources.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth2 token is correctly set up and has sufficient permissions.
- Empty Title or Description: While these fields may be optional, sending empty strings might overwrite existing values unintentionally. Confirm intended updates before execution.
- Network Issues: Connectivity problems can cause request timeouts or failures. Check network access and API endpoint availability.