Actions80
- Todos Actions
- 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
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 content of a task card after receiving new information.
- Changing the due date of a card to reflect deadline extensions.
- Reassigning tasks to different team members by updating assignee IDs.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket containing the card to update (required). |
| Card Id | The unique identifier of the card to update within the specified bucket (required). |
| Title | The new title for the card. |
| Content | The new content or description of 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. Example: [123, 456]. |
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 represent any file attachments or media associated with the card, but this is not indicated in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API service.
- The node uses the Basecamp API endpoint, which requires the Basecamp account ID to construct the base URL.
- Proper configuration of authentication credentials in n8n is necessary for successful API calls.
Troubleshooting
- Missing Required Fields: Errors may occur if
Bucket IdorCard Idare not provided or invalid. Ensure these IDs correspond to existing resources. - Invalid JSON in Assignee Ids: The
assignee_idsproperty expects a valid JSON array. Malformed JSON will cause parsing errors. - Authentication Failures: If the API key or OAuth token is missing or expired, the node will fail to authenticate. Verify credentials are correctly set up.
- API Rate Limits: Frequent updates might hit API rate limits; handle such errors by implementing retries or backoff strategies.
- Incorrect Date Format: The
Due Onfield should be in a recognized date string format. Invalid formats may cause the API to reject the request.