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 retrieve detailed information about a specific to-do item within a project (referred to as a "bucket" in Basecamp). It is designed to fetch a single to-do by its unique ID from a specified project. This functionality is useful for workflows that need to access or process individual task details, such as tracking task status, updating dashboards, or integrating task data into other systems.
Practical examples:
- Automatically fetching a to-do's details when triggered by an event, to update a project management dashboard.
- Retrieving a to-do's information to send reminders or notifications based on its status or due date.
- Integrating Basecamp tasks with other tools by pulling specific to-do data for further processing.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the to-do resides. Used in the API endpoint path. |
| To-Do ID | The unique ID of the to-do item to retrieve. Used in the API endpoint path. |
| Return Full Response | Whether to return the full HTTP response including status code and headers, instead of only the response body. |
Output
The node outputs JSON data representing the to-do item retrieved from Basecamp. This includes all details provided by the Basecamp API for that to-do, such as title, description, status, assignees, due dates, and other metadata.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, containing status code, headers, and body, allowing advanced users to handle response metadata.
The node does not output binary data.
Dependencies
- Requires an API authentication token configured in n8n credentials to authenticate requests to the Basecamp API.
- Needs the Basecamp account ID to construct the correct API base URL.
- The node depends on the Basecamp API being accessible and the user having appropriate permissions to read to-dos in the specified project.
Troubleshooting
Common issues:
- Invalid or missing Project ID or To-Do ID will cause the API request to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
- 404 Not Found: The specified project or to-do ID does not exist. Verify IDs are correct.
- 401 Unauthorized: Authentication failed. Check that the API key or OAuth token is valid and has required scopes.
- 400 Bad Request: Input parameters might be malformed or missing. Ensure Project ID and To-Do ID are provided and valid numbers.
- 500 Internal Server Error: Temporary server issue; retry after some time or check Basecamp service status.