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 change the color of a specific column within a card table in a project management or organizational tool that supports card tables. By specifying the bucket and column identifiers along with the desired color, users can visually categorize or highlight columns for better clarity and organization.
Common scenarios include:
- Highlighting priority columns in a project board.
- Color-coding columns based on status or category.
- Customizing the appearance of card tables to improve visual workflow.
For example, you might use this node to set the "In Progress" column to blue and the "Completed" column to green, making it easier for team members to quickly identify task statuses.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (a grouping container) where the target column exists. |
| Column Id | The numeric identifier of the column whose color you want to change. |
| Color | The new color to apply to the column. Options: White, Red, Orange, Yellow, Green, Blue, Aqua, Purple, Gray, Pink, Brown. |
Output
The node outputs JSON data representing the result of the color change operation. This typically includes confirmation of the update or details about the modified column. There is no binary data output.
Dependencies
- Requires an API key credential for authentication with the external service managing the card tables.
- The node sends HTTP requests to the service's API endpoint configured with the appropriate base URL and headers.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Bucket or Column Id: If the specified bucket or column ID does not exist, the API may return an error. Verify the IDs before running the node.
- Unauthorized Access: Ensure the API key or authentication token has sufficient permissions to modify card tables.
- Unsupported Color Value: Only the predefined color options are accepted. Using an unsupported color will cause the request to fail.
- Network Issues: Connectivity problems can prevent the node from reaching the API endpoint. Check network settings and API availability.
Links and References
- Refer to the official API documentation of the card table service for detailed information on bucket and column identifiers and color options.
- Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.