Actions80
- Todos Actions
- 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
Overview
This node operation allows you to create a new column within a specified card table in a card-based organizational system. It is useful for dynamically adding structure to card tables by defining columns that can hold specific types of information. For example, you might use this operation to add a "Status" column or a "Due Date" column to a project management board.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket containing the card table where the new column will be added. |
| Card Table Id | The identifier of the 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.
If the node supports binary data output (not indicated here), it would represent any file or media associated with the column creation response, but this operation primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing card tables.
- The node uses a base URL constructed dynamically from credentials, indicating the need for proper configuration of authentication and endpoint details in n8n.
- No additional external dependencies are indicated in the provided source code snippet.
Troubleshooting
- Missing Required Fields: Ensure that
Bucket Id,Card Table Id, andTitleare provided; these are mandatory. - Authentication Errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Invalid IDs: Confirm that the bucket and card table IDs exist and are accessible with the provided credentials.
- API Rate Limits: If requests fail due to rate limiting, consider implementing retry logic or reducing request frequency.
Links and References
- Refer to the official API documentation of the card table service for detailed information on creating columns and required parameters.
- Consult n8n documentation on how to configure API credentials and handle HTTP request errors.