Actions119
- 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
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
This node interacts with the Basecamp API to reposition a to-do list group within a specified project (bucket). It allows users to change the order of to-do list groups by specifying a new position index. This is useful for organizing tasks and groups in a way that reflects priority or workflow changes.
Common scenarios include:
- Reordering task groups after project reprioritization.
- Adjusting the layout of to-do lists to match team preferences.
- Automating task group management as part of larger workflow automations.
Example: Moving a to-do list group from position 3 to position 1 within a project to highlight its urgency.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the to-do list group exists. Used in the API path. |
| Group ID | The ID of the to-do list group to be repositioned. Used in the API path. |
| Position | The new position index for the to-do list group within the project. |
| Return Full Response | Whether to return the full HTTP response (status code, headers, body) or only the body. |
Output
The node outputs JSON data representing the result of the reposition operation. By default, it returns only the response body, which typically contains confirmation or details about the updated to-do list group.
If "Return Full Response" is enabled, the output includes the entire HTTP response object, including status code, headers, and body, allowing for more detailed handling or debugging.
No binary data output is involved in this operation.
Dependencies
- Requires an authenticated connection to the Basecamp API via an OAuth2 credential or equivalent API authentication token.
- The node uses the Basecamp account ID to construct the API base URL.
- Proper permissions on the Basecamp account are necessary to modify to-do list groups.
Troubleshooting
- Invalid Project or Group ID: If the provided IDs do not exist or the user lacks access, the API will return an error. Verify IDs and permissions.
- Position Out of Range: Providing a position value outside the valid range may cause errors or unexpected behavior. Ensure the position is within the bounds of existing groups.
- Authentication Errors: Missing or invalid API credentials will prevent the request from succeeding. Confirm that the API key or OAuth token is correctly configured.
- API Rate Limits: Excessive requests might trigger rate limiting. Implement retries or backoff strategies if needed.
- Return Full Response Misuse: Enabling full response output changes the structure of the output; downstream nodes must handle this accordingly.