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 "Add On Hold Section" for the "Card Tables" resource interacts with a project management or task tracking system that uses card tables (similar to Kanban boards). The operation adds a special "On Hold" section within a specified column of a card table bucket. This is useful for visually segregating tasks or cards that are temporarily paused or waiting on external factors, helping teams manage workflow states more effectively.
Practical examples:
- In a software development board, you might add an "On Hold" section in the "In Progress" column to mark features blocked by dependencies.
- In a customer support board, placing tickets "On Hold" can indicate waiting for customer response or third-party input.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (a grouping container) where the "On Hold" section will be added. |
| Column Id | Numeric identifier of the column within the bucket where the "On Hold" section should be created. |
Output
The node outputs JSON data representing the result of adding the "On Hold" section. This typically includes details about the newly created section such as its ID, name, and placement within the specified column and bucket. The exact structure depends on the API response but generally confirms successful creation and provides metadata for further use.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API or equivalent service managing card tables.
- The node relies on the Basecamp API endpoint configured dynamically using the user's credentials.
- Proper permissions to modify card tables and columns are necessary.
Troubleshooting
- Common issues:
- Invalid or missing Bucket Id or Column Id leading to errors like "Bucket not found" or "Column does not exist".
- Authentication failures due to incorrect or expired API credentials.
- Insufficient permissions to modify the specified bucket or column.
- Error messages:
- "Unauthorized" or "Authentication failed": Check API key validity and refresh tokens if applicable.
- "Resource not found": Verify that the Bucket Id and Column Id are correct and exist in the target workspace.
- "Permission denied": Ensure the authenticated user has rights to edit the card tables.
Links and References
- Basecamp API Documentation
- General Kanban board concepts: https://en.wikipedia.org/wiki/Kanban_(development)
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/