Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node interacts with the Basecamp API to update a specific column within a card table (a project management feature in Basecamp). It allows users to modify properties of a column such as its title or description. This is useful for automating updates to project boards, keeping task columns current without manual intervention.
Practical examples include:
- Renaming a column to reflect a change in workflow stage.
- Updating the description of a column to provide clearer instructions or context.
- Integrating with other tools to dynamically adjust project board columns based on external events.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the card table resides; used in the API path. |
| Column ID | The numeric ID of the column to update; used in the API path. |
| Column Fields | The fields of the column to update. Options include: |
| - Title: New title string for the column. | |
| - Description: New description string for the column. | |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the updated column information returned by the Basecamp API. If "Return Full Response" is enabled, the output includes the entire HTTP response object with status code, headers, and body; otherwise, only the response body is returned.
No binary data output is involved.
Dependencies
- Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
- Needs the Basecamp account ID configured in the node's credentials to construct the API base URL.
- The node sends requests to the Basecamp API endpoint corresponding to the specified project and column IDs.
Troubleshooting
- Invalid Project or Column ID: Errors may occur if the provided project or column IDs do not exist or are incorrect. Verify these IDs in Basecamp before running the node.
- Authentication Errors: Ensure that the OAuth2 credentials are valid and have sufficient permissions to update card table columns.
- API Rate Limits: Frequent updates might hit Basecamp API rate limits; handle errors accordingly.
- Empty or Invalid Field Values: Providing empty strings or invalid types for title or description may cause the API to reject the request.
Common error messages:
- Unauthorized or 401 errors indicate authentication issues.
- 404 Not Found suggests incorrect project or column IDs.
- 400 Bad Request may indicate malformed input data.
Resolving these typically involves verifying credentials, checking IDs, and ensuring input data correctness.