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 integrates with the Basecamp API to create a new to-do list within a specified project and to-do set. It is useful for automating task management workflows by programmatically adding organized to-do lists to projects in Basecamp. For example, a project manager can use this node to automatically generate daily or weekly task lists based on external triggers or data sources, ensuring that team members have up-to-date task lists without manual input.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the to-do list will be created. |
| todosetId | The numeric ID of the to-do set under which the to-do list will be added. |
| Name | The name/title of the to-do list to be created. |
| Description | Optional HTML-supported description providing additional details about the to-do list. |
| 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 newly created to-do list as returned by the Basecamp API. This typically includes details such as the to-do list's unique ID, name, description, creation timestamps, and related 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 for more detailed handling of the API response.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project (bucket) and to-do set IDs.
- Proper API credentials must be configured in n8n to authorize requests.
Troubleshooting
- Invalid Project or To-do Set ID: If the provided IDs do not exist or the authenticated user lacks access, the API will return an error. Verify that the IDs are correct and accessible.
- Authentication Errors: Ensure that the OAuth2 credentials are valid and have sufficient permissions to create to-do lists.
- Missing Required Fields: The "Name", "Project ID", and "todosetId" fields are mandatory. Omitting these will cause the request to fail.
- HTML in Description: Since the description may contain HTML, ensure it is properly formatted to avoid API rejection.
- API Rate Limits: Excessive requests might lead to rate limiting; handle such errors by implementing retries or backoff strategies.