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 creates a new column within a specified card table in a card-based organizational system. It is useful for users who want to dynamically add columns to their card tables, allowing them to customize the structure and organization of their data or project boards. For example, a project manager could use this node to add a "Status" column to track task progress or a "Priority" column to highlight urgent items.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket that contains the card table where the column will be added. |
| Card Table Id | The identifier of the specific card table to which the new column will be added. |
| Title | The title or name of the new column being created. |
| Description | An optional description providing additional details about the new column. |
Output
The output JSON contains the details of the newly created column, typically including its unique identifier, title, description, and any other metadata returned by the API. This allows subsequent nodes or workflows to reference or manipulate the newly created column. There is no indication that binary data is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing card tables.
- The node uses a base URL constructed dynamically from credentials (e.g., a Basecamp ID), so proper configuration of credentials and environment variables is necessary.
- The node depends on an OpenAPI specification for request construction and validation.
Troubleshooting
- Missing Required Fields: Ensure that
Bucket Id,Card Table Id, andTitleare provided; otherwise, the API call will fail. - Authentication Errors: Verify that the API key or OAuth token is correctly configured and has sufficient permissions.
- Invalid IDs: Providing incorrect bucket or card table IDs will result in errors; confirm these IDs exist and belong to the authenticated user/account.
- Network Issues: Check network connectivity and API endpoint availability if requests time out or fail.
Links and References
- Refer to the official API documentation of the card table service for detailed information on creating columns.
- Consult n8n documentation on how to configure API credentials and use custom nodes with OpenAPI specifications.