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, specifically focusing on managing cards within a Card Table resource. The "Move a Card" operation allows users to move a card from one column to another within a specified project (bucket). This is useful for automating task or item management workflows where cards represent tasks, ideas, or items that need to be organized dynamically across different columns (e.g., stages of progress).
Practical examples include:
- Automatically moving a task card to a "Completed" column when a related process finishes.
- Reorganizing cards based on priority changes or status updates triggered by other systems.
- Integrating with external tools to reflect real-time changes in project boards.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the card resides; used in the API endpoint path. |
| cardId | The unique identifier of the card to be moved; used in the API endpoint path. |
| Target Column ID | The ID of the target column where the card should be moved. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The output contains a JSON object representing the response from the Basecamp API after attempting to move the card. If "Return Full Response" is set to false, only the response body is returned, which typically includes details about the moved card or confirmation of the move action.
If "Return Full Response" is true, the output includes the entire HTTP response, including status code and headers, which can be useful for debugging or advanced handling.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to access and modify card tables.
- The node expects the user to provide valid project (bucket) IDs and card IDs.
- No additional external dependencies beyond the Basecamp API and its authentication are required.
Troubleshooting
- Invalid Project or Card ID: Errors may occur if the provided project ID or card ID does not exist or the authenticated user lacks access. Verify IDs and permissions.
- Target Column ID Issues: Ensure the target column ID exists within the specified project and is valid.
- Authentication Failures: If the API key or OAuth token is invalid or expired, the request will fail. Refresh or reconfigure credentials as needed.
- API Rate Limits: Excessive requests might trigger rate limiting; handle such errors by implementing retries or backoff strategies.
- Unexpected Response Structure: If "Return Full Response" is enabled, downstream nodes must handle the full HTTP response structure properly.