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
Schedule Entry → Update a Schedule Entry
AI-generatedOverview
This node operation updates an existing schedule entry in a Basecamp project. It allows users to modify details such as the start and end date/time, summary, description, participant IDs, all-day event status, and notification preferences. This is useful for managing and adjusting scheduled events within a project, ensuring that all participants have up-to-date information.
Use Case Examples
- Updating the start and end times of a meeting schedule entry.
- Changing the summary and description of a project milestone event.
- Adding or removing participants from a schedule entry.
- Marking an event as an all-day event or enabling notifications for participants.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) used in the API endpoint path to specify which project the schedule entry belongs to. |
| entryId | The ID of the schedule entry to update, used in the API endpoint path to identify the specific entry. |
| Start Date/Time | The new start date and time for the schedule entry. If left empty, the existing start time remains unchanged. |
| End Date/Time | The new end date and time for the schedule entry. If left empty, the existing end time remains unchanged. |
| Entry Fields | Additional fields to update in the schedule entry, including summary, description, participant IDs, all-day event status, and notification preference. |
| Return Full Response | Whether to return the full API response including status code, headers, and body instead of only the response body. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
statusCode- HTTP status code of the API response.headers- Headers returned in the API response.body- The main content of the API response, typically the updated schedule entry details.
Dependencies
- Basecamp API with OAuth2 authentication
Troubleshooting
- Ensure the Project ID and entryId are correct and correspond to existing resources in Basecamp to avoid 404 errors.
- If the API returns authentication errors, verify that the OAuth2 credentials are valid and have the necessary permissions.
- Timeout errors may occur if the server is slow to respond; consider increasing the timeout setting in Request Options.
- If SSL certificate validation fails and you trust the endpoint, enable the 'Ignore SSL Issues' option to bypass validation.
Links
- Basecamp API Documentation - Official documentation for Basecamp API endpoints and usage.