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 "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 bucket and column of a card table. 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 include:
- Marking tasks that cannot proceed due to dependencies.
- Highlighting issues awaiting client feedback.
- Separating blocked work items from active ones in a sprint board.
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 will 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 possibly metadata confirming successful creation. The exact structure depends on the API response but generally confirms the addition of the section in the specified location.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the external service managing the card tables.
- The node relies on the Basecamp API (as inferred from bundled code references), so a valid Basecamp account and appropriate permissions are necessary.
- Network connectivity to the Basecamp API endpoint is required.
Troubleshooting
- Invalid Bucket or Column Id: If the provided IDs do not exist or are incorrect, the API may return errors indicating resource not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Permission Denied: Insufficient permissions on the Basecamp project or workspace can prevent section creation.
- API Rate Limits: Excessive requests might trigger rate limiting; handle retries or backoff accordingly.