Actions80
- 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
- Todos Actions
Overview
This node operation updates an existing card within a specified bucket in a Card Tables resource. It allows users to modify various attributes of a card such as its title, content, due date, and assignees. This is useful in project management or task tracking scenarios where cards represent tasks or items that need updating as progress is made or details change.
Practical examples include:
- Changing the title or description of a task card to reflect updated requirements.
- Setting or modifying the due date for a task.
- Assigning or reassigning team members responsible for the card.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket containing the card to update. |
| Card Id | The unique identifier of the card to be updated. |
| Title | The new title for the card. |
| Content | The new content or description for the card. |
| Due On | The due date for the card, typically in string format (e.g., ISO 8601 date string). |
| Assignee Ids | A JSON array of user IDs to assign to the card. |
Output
The node outputs JSON data representing the updated card object returned from the API after the update operation. This JSON includes the current state of the card with all updated fields.
If the node supports binary data output, it would typically relate to attachments or media associated with the card, but this operation focuses on updating textual and metadata fields only.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint specific to the user's account (base URL constructed using the Basecamp account ID).
- Proper permissions are needed on the Basecamp account to update cards within buckets.
Troubleshooting
- Invalid Bucket Id or Card Id: If these IDs do not exist or the user lacks access, the API will return an error. Verify the IDs and permissions.
- Malformed JSON in Assignee Ids: The
assignee_idsproperty expects a valid JSON array. Invalid JSON will cause parsing errors. Ensure correct JSON formatting. - Missing Required Fields: Both Bucket Id and Card Id are required. Omitting them will result in validation errors.
- API Authentication Errors: Ensure the API key or OAuth token is valid and has not expired.
- Date Format Issues: The
due_onfield should be in a recognized date string format. Incorrect formats may cause the API to reject the request.