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 operation updates an existing schedule entry within a specified project (bucket) in Basecamp. It allows users to modify details such as start and end times, summary, description, participants, all-day status, and notification preferences for the schedule entry.
Common scenarios where this node is beneficial include:
- Adjusting meeting times or event durations after initial scheduling.
- Updating event descriptions or participant lists dynamically based on workflow conditions.
- Changing notification settings to control whether participants receive alerts about changes.
Practical example: Automatically update a project meeting's start and end times and notify all participants when a related task deadline shifts.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the schedule entry; used in API path. |
| entryId | The numeric ID of the schedule entry to update; used in API path. |
| Start Date/Time | When the schedule entry starts; leave empty to keep the current start time. |
| End Date/Time | When the schedule entry ends; leave empty to keep the current end time. |
| Entry Fields | Additional fields to update in the schedule entry: |
| - Summary | Brief summary describing the schedule entry. |
| - Description | Detailed information about the entry; may contain HTML content. |
| - Participant IDs | Comma-separated string of participant IDs involved in the entry. |
| - All Day Event | Boolean indicating if the event lasts all day. |
| - Send Notifications | Boolean indicating whether to notify participants about the update. |
| Return Full Response | Boolean to decide if the full HTTP response (status, headers, body) should be returned instead of just the body. |
Output
The node outputs JSON data representing the updated schedule entry as returned by the Basecamp API. This typically includes the updated fields such as start/end times, summary, description, participant IDs, and other metadata.
If "Return Full Response" is enabled, the output will include the entire HTTP response object with status code, headers, and body.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to update schedule entries.
- The node expects the Basecamp account ID to be configured in credentials to construct the API endpoint URL.
- No additional external services or environment variables are required beyond the Basecamp API credentials.
Troubleshooting
- Invalid Project or Entry ID: If the provided project or schedule entry ID does not exist or is incorrect, the API will return an error. Verify IDs before running the node.
- Insufficient Permissions: Ensure the API credentials have rights to update schedule entries in the specified project.
- Date/Time Format Issues: The start and end date/time must be valid ISO 8601 strings. Invalid formats may cause request failures.
- Empty Required Fields: Project ID and entry ID are mandatory; missing these will prevent the request from being sent.
- Notification Failures: If notifications are enabled but participants are invalid or unreachable, notifications may fail silently or generate warnings.