Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
The "Update Schedule" operation in the Schedules resource allows users to modify an existing schedule within a specified bucket. This node is useful for managing and updating scheduling details programmatically, such as adjusting due dates or toggling whether the schedule should include due assignments from related to-dos, cards, and steps. Practical applications include automating project timeline adjustments or synchronizing schedule changes with other tools.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket that contains the schedule to update. |
| Schedule Id | The unique identifier of the schedule to be updated. |
| Include Due Assignments | A boolean flag indicating whether the schedule should include due dates from to-dos, cards, and steps. Possible values: true or false. |
Output
The node outputs JSON data representing the updated schedule object as returned by the Basecamp API. This typically includes updated schedule details such as IDs, timestamps, and any modified properties reflecting the changes made. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the user's Basecamp account ID.
- Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id or Schedule Id will cause the update to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and has sufficient permissions.
- "Not Found": Verify that the Bucket Id and Schedule Id are correct and exist in the Basecamp account.
- "Bad Request": Ensure that the input parameters, especially the boolean flag for including due assignments, are valid.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API integration basics)