Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node operation updates an existing card within a specified bucket in a Card Table system. It allows users to modify key attributes of a card such as its title, content, due date, and assigned users. This is useful for project management workflows where task details need to be updated dynamically based on progress or changes in requirements.
Practical examples include:
- Updating the description or status of a task card after a meeting.
- Changing the due date of a card when deadlines shift.
- Reassigning tasks to different team members as workload changes.
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 new 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 the card to. |
Output
The node outputs JSON data representing the updated card object as returned by the API. This includes all the card's properties after the update, reflecting any changes made during execution.
If the node supports binary data output, it would typically relate to attachments or files associated with the card, but this operation focuses on updating textual and metadata fields only.
Dependencies
- Requires an API key credential for authenticating requests to the Basecamp API.
- Needs the Basecamp account ID configured in credentials to construct the base URL for API calls.
- Depends on the Basecamp API being accessible and responsive.
Troubleshooting
- Invalid Bucket Id or Card Id: If these identifiers are incorrect or do not exist, the API will return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and account ID are correctly set up.
- Malformed JSON in Assignee Ids: The
assignee_idsproperty expects a valid JSON array. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting. - Date Format Issues: The
due_onfield should be in a recognized date string format. Incorrect formats may lead to API rejection or unexpected behavior.