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 allows you to move a card within a card table system by specifying the target column where the card should be moved. It is useful in project management or task tracking scenarios where cards represent tasks, issues, or items that need to be reorganized across different columns (e.g., stages of progress). For example, moving a task card from "To Do" to "In Progress" column to reflect its current status.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket (a container or grouping) that holds the card. |
| Card Id | The unique identifier of the card that you want to move. |
| Column Id | The identifier of the destination column where the card will be moved. |
Output
The output JSON typically contains the updated card information after it has been moved to the new column. This may include details such as the card's new position, column id, and any other metadata returned by the API confirming the successful move.
If the node supports binary data output, it would generally relate to attachments or media associated with the card, but this operation primarily deals with JSON data representing card movement.
Dependencies
- Requires an API key credential for authentication with the Basecamp API.
- The node uses the Basecamp API endpoint, which requires the base URL constructed using the user's Basecamp account ID.
- Proper network access to the Basecamp API service is necessary.
Troubleshooting
- Invalid IDs: Errors may occur if the provided Bucket Id, Card Id, or Column Id do not exist or are incorrect. Verify these IDs before running the node.
- Authentication errors: Ensure the API key or OAuth token is valid and has sufficient permissions to modify cards.
- API rate limits: If too many requests are made in a short time, the API might throttle requests. Implement retries or backoff strategies.
- Network issues: Connectivity problems can cause request failures; check your internet connection and firewall settings.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Node (for understanding how API calls are made)