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 key attributes of a card such as its title, content, due date, and assigned users. 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 after receiving new information.
- Updating the due date of a card to reflect a deadline extension.
- Modifying the list of assignees responsible for the card.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket containing the card to update. |
| Card Id | The numeric identifier of the card to be updated. |
| Title | The new title text for the card. |
| Content | The new content or description text 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 to the card. |
Output
The node outputs JSON data representing the updated card object returned from the API. This typically includes the card's updated fields such as id, title, content, due date, assignees, and other metadata reflecting the current state after the update.
If the node supports binary data output, it would generally relate to attachments or files associated with the card, but this operation focuses on updating textual and relational data only.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the Basecamp API.
- Needs the Basecamp account ID to construct the base URL for API requests.
- Depends on the Basecamp API being available 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 authorization failures. Ensure the API key/token is correctly set up in n8n.
- 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.
Links and References
- Basecamp API Documentation - Official API docs for understanding card and bucket resources.
- n8n Documentation - For general guidance on using and configuring nodes and credentials.