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 item within a specified project and to-do list. It is useful for automating task management workflows, such as adding tasks programmatically when certain triggers occur (e.g., form submissions, issue tracking updates, or calendar events). For example, you can automatically create a to-do in a project’s task list when a new customer support ticket is received, ensuring timely follow-up.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the to-do will be created. |
| todolistId | The numeric ID of the to-do list within the project where the to-do will be added. |
| Content | The title or main content of the to-do item. |
| Description | Optional detailed description of the to-do; supports HTML formatting. |
| Assignee IDs | Comma-separated string of user IDs to assign the to-do to. |
| Completion Subscriber IDs | Comma-separated string of user IDs to notify upon completion of the to-do. |
| Send Notifications | Boolean flag indicating whether assignees should be notified about their assignment. |
| Due Date | Due date for the to-do in ISO date format (YYYY-MM-DD). |
| Start Date | Start date for the to-do in ISO date format (YYYY-MM-DD). |
| Return Full Response | Boolean flag to return the full HTTP response (status code, headers, body) instead of just body. |
Output
The node outputs JSON data representing the newly created to-do item as returned by the Basecamp API. This typically includes fields such as the to-do's ID, content, description, assigned users, dates, and status. If "Return Full Response" is enabled, the output includes the entire HTTP response object with status code and headers, which can be useful for debugging or advanced handling.
No binary data is produced by this node.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and to-do list IDs that exist in the Basecamp account.
- Proper permissions are needed on the Basecamp side to create to-dos within the specified project.
Troubleshooting
- Invalid Project or To-do List ID: If the provided IDs do not exist or the authenticated user lacks access, the API will return an error. Verify IDs and permissions.
- Missing Required Fields: The node requires at least Project ID, To-do List ID, and Content. Omitting these will cause errors.
- Date Format Issues: Ensure due and start dates are in the correct ISO format (YYYY-MM-DD). Incorrect formats may lead to API rejection.
- Notification Failures: If notification flags are set but assignee IDs are invalid or missing, notifications may not be sent.
- API Rate Limits: Excessive requests may trigger rate limiting by Basecamp. Implement retries or backoff as needed.