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
The "Move Column" operation within the "Card Tables" resource allows users to reorder columns in a card table by moving a specified column (source) to a new position relative to another column (target). This is useful for organizing data visually in project management or task tracking tools that use card tables, enabling users to customize the layout according to their workflow preferences.
Practical examples include:
- Moving a priority column next to the status column to better visualize task urgency.
- Reordering columns after adding new ones to maintain logical grouping.
- Adjusting the display order of columns dynamically based on user roles or project phases.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket containing the card table. |
| Card Table Id | Numeric identifier of the specific card table where the column move will occur. |
| Source Id | Numeric identifier of the column to be moved. |
| Target Id | Numeric identifier of the column that will serve as the reference point for positioning. |
| Position | Numeric value indicating the new position relative to the target column (e.g., before or after). |
Output
The node outputs JSON data representing the result of the move column operation. Typically, this includes confirmation of the updated column order or details about the moved column. The exact structure depends on the API response but generally contains identifiers and status information confirming the successful repositioning.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint configured with the user's Basecamp account ID.
- Proper permissions on the Basecamp account to modify card tables and columns are necessary.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id, Card Table Id, Source Id, or Target Id can cause failures.
- Insufficient permissions to modify the card table.
- Network or authentication errors when connecting to the Basecamp API.
Error Messages:
- "Resource not found" — Verify that the Bucket Id, Card Table Id, Source Id, and Target Id are correct and exist.
- "Unauthorized" — Check that the API key credential is valid and has appropriate scopes.
- "Invalid position value" — Ensure the position parameter is within acceptable bounds (usually 1 or greater).
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring network connectivity.