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
The "Update a Card" operation in the Card Table resource allows users to modify details of an existing card within a project (referred to as a bucket). This node is useful for updating task cards with new information such as changing the title, content, due date, or assignees. It is beneficial in scenarios where project management workflows require dynamic updates to task cards, for example, adjusting deadlines, reassigning tasks, or refining task descriptions.
Practical examples include:
- Updating the due date of a task card when project timelines shift.
- Changing the assignees of a card to reflect team member availability.
- Editing the content or title of a card to clarify task requirements.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the card; used in the API endpoint path. |
| Card ID | The numeric ID of the card to update; used in the API endpoint path. |
| Due Date | The due date for the card in ISO date format (YYYY-MM-DD). Leave empty to remove the due date. |
| Card Fields | A collection of fields to update on the card: |
| - Title: The new title string for the card. | |
| - Content: The new content/description of the card, supports HTML formatting. | |
| - Assignee IDs: JSON array string of person IDs to assign to the card. | |
| 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 card information returned from the API. If the "Return Full Response" property is enabled, the output includes the entire HTTP response object, which contains status code, headers, and body. Otherwise, only the response body (the updated card data) is returned.
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 update cards.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
- Invalid Project ID or Card ID: Errors may occur if the provided project or card IDs do not exist or the user lacks permission. Verify IDs and access rights.
- Malformed Assignee IDs: The assignee IDs must be a valid JSON array string. Invalid JSON will cause request failures.
- Due Date Format Issues: The due date should be in ISO date format (YYYY-MM-DD). Incorrect formats may lead to errors or ignored values.
- API Authentication Errors: Ensure that the OAuth2 credentials are valid and have not expired.
- Empty Required Fields: Project ID and Card ID are mandatory; missing these will prevent the request from being sent.
Common error messages typically relate to authorization failures, invalid input data, or resource not found. Checking the full response (by enabling "Return Full Response") can help diagnose issues by providing HTTP status codes and error messages.