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 allows users to interact with the Basecamp API, specifically to reposition a to-do item within a project (referred to as a "bucket" in Basecamp). Repositioning a to-do changes its order or priority within the list of tasks. This is useful for task management workflows where the order of to-dos reflects their urgency or sequence.
Common scenarios include:
- Adjusting task priorities dynamically based on changing project needs.
- Organizing to-dos after adding or completing other tasks.
- Automating task reordering as part of larger workflow automations.
For example, if a user wants to move a specific to-do to the top of the list, they can specify the new position as 1, and the node will update the to-do's position accordingly.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) containing the to-do. Used in the API endpoint path. |
| todoId | The ID of the to-do item to reposition. Used in the API endpoint path. |
| Position | The new position for the to-do (1-based index). Specifies where the to-do should be moved. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the result of the reposition operation. By default, it returns only the response body from the Basecamp API, which typically includes details about the updated to-do or confirmation of the reposition action.
If the "Return Full Response" property is set to true, the output will include the entire HTTP response object, including status code, headers, and body, allowing for more detailed handling or debugging.
The node does not output binary data.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and to-do IDs.
- No additional external dependencies beyond the Basecamp API and proper credentials.
Troubleshooting
- Invalid Project or To-Do ID: If the provided IDs do not exist or are incorrect, the API will return an error. Verify that the IDs correspond to existing resources in your Basecamp account.
- Insufficient Permissions: Ensure the API credentials have permission to modify to-dos in the specified project.
- Position Out of Range: Providing a position number outside the valid range (e.g., less than 1 or greater than the number of to-dos) may cause errors or unexpected behavior. Use valid positions within the current to-do list length.
- API Rate Limits: Frequent repositioning requests might hit Basecamp API rate limits; handle such errors by retrying after some delay.
- Return Full Response Confusion: When enabling "Return Full Response," the output structure changes. Make sure downstream nodes or workflows expect this format.