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
The "Update a Schedule" operation in the Schedule resource allows users to modify an existing schedule within a specified project (bucket) in Basecamp. This node is useful for automating updates to schedules, such as changing whether due assignments from to-dos, cards, and steps are included in the schedule. Practical scenarios include adjusting schedules dynamically based on project progress or external triggers, ensuring that team members always have up-to-date scheduling information.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the schedule exists; used in the API endpoint path. |
| Schedule ID | The numeric ID of the schedule to update; used in the API endpoint path. |
| Include Due Assignments | Boolean option indicating whether the schedule should include due dates from to-dos, cards, and steps. Possible values: true or false. |
| Return Full Response | Boolean flag to determine if the node returns the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the updated schedule object returned by the Basecamp API. If the "Return Full Response" property is enabled, the output will include the entire HTTP response including status code and headers, otherwise only the response body (the updated schedule details) is returned.
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 and schedule IDs.
- Proper API permissions are necessary to update schedules within the specified project.
Troubleshooting
- Invalid Project or Schedule ID: Errors may occur if the provided project or schedule ID does not exist or the authenticated user lacks access. Verify IDs and permissions.
- API Authentication Errors: Ensure the OAuth2 credentials are correctly configured and have not expired.
- Invalid Field Values: Providing incorrect types or unsupported fields in the schedule update payload can cause API errors. Use boolean values for "Include Due Assignments".
- Network Issues: Connectivity problems with the Basecamp API endpoint can result in timeouts or failed requests.
Common error messages:
- 404 Not Found: The specified project or schedule ID was not found.
- 401 Unauthorized: Authentication failed; check API credentials.
- 400 Bad Request: Invalid input data; verify field names and types.