Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node operation allows you to move a column within a card table in a project management context. Specifically, it targets a "Card Table" resource and performs the "Move a Column" operation. This is useful when you want to reorder columns in a card table to better organize tasks, data, or workflow stages.
Common scenarios include:
- Adjusting the order of task categories or statuses in a project board.
- Reorganizing columns to reflect priority changes or workflow updates.
- Automating column rearrangement based on external triggers or conditions.
For example, if you have a card table representing different phases of a project, you can programmatically move a column from one position to another to reflect a change in process flow.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the card table resides; used in the API path. |
| cardTableId | The numeric ID of the specific card table to modify; used in the API path. |
| Source Column ID | The numeric ID of the column you want to move. |
| Target Position ID | The numeric ID indicating the target position for the moved column. |
| Position | The numeric index specifying the new position of the column within the card table. |
| Return Full Response | Boolean flag to determine whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The output JSON contains the response from the Basecamp API after moving the column. It typically includes details about the updated card table or confirmation of the move operation.
If "Return Full Response" is enabled, the output will include the full HTTP response with status code, headers, and body, allowing for more detailed handling or debugging.
No binary data is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- Needs the account ID configured in credentials to construct the API base URL.
- The node depends on the Basecamp API endpoints for card tables and columns.
Troubleshooting
- Invalid IDs: Ensure that the Project ID, Card Table ID, Source Column ID, and Target Position ID are correct and correspond to existing entities in Basecamp.
- Permission Errors: The API key or OAuth token must have sufficient permissions to modify card tables.
- Position Conflicts: Providing an invalid position number may cause errors; verify that the position is within the valid range of columns.
- API Rate Limits: Frequent calls might hit rate limits imposed by Basecamp; handle such errors by retrying after some delay.
- Return Full Response Misuse: If "Return Full Response" is enabled but not handled properly downstream, it may cause unexpected data formats.