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 allows you to create a new column within a specified card table in a project management or organizational tool that uses "Card Tables" and "Buckets" as structural elements. It is useful for dynamically adding columns to organize cards or tasks under different categories or stages.
Common scenarios include:
- Adding a new category or status column to a Kanban-style board.
- Structuring data by creating custom columns for specific workflows.
- Expanding existing card tables with additional metadata fields.
For example, if you have a card table representing project tasks divided into buckets (like sprints or phases), you can add a new column titled "Priority" to classify tasks by urgency.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket where the new column will be created. |
| Card Table Id | The numeric identifier of the card table to which the column belongs. |
| Title | The title or name of the new column to be created. |
| Description | An optional description providing more details about the purpose or content of the column. |
Output
The node outputs JSON data representing the newly created column object. This typically includes the column's unique ID, title, description, and any other metadata returned by the API after creation.
If the node supports binary data output, it would relate to attachments or media associated with the column, but based on the provided code and properties, this operation focuses on JSON data only.
Dependencies
- Requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the external service managing card tables.
- The base URL for API requests is constructed dynamically using credentials (e.g., a Basecamp ID).
- The node depends on an OpenAPI specification bundled internally to define request structure and parameters.
Troubleshooting
- Missing Required Fields: Ensure that
Bucket Id,Card Table Id, andTitleare provided; otherwise, the API will reject the request. - Authentication Errors: Verify that the API authentication token or credentials are correctly set up in n8n.
- Invalid IDs: Using non-existent bucket or card table IDs will cause errors; confirm these IDs exist in your system.
- Network Issues: Check connectivity to the external API endpoint and ensure no firewall or proxy blocks the requests.
Links and References
- Refer to the external service’s API documentation for detailed information on card tables and columns.
- n8n documentation on creating custom nodes for further customization guidance.