Basecamp icon

Basecamp

Interact with the Basecamp API
Join our community

Actions80

Overview

This node updates an existing schedule entry in a specified bucket within a scheduling system. It is useful for modifying details of calendar events or appointments, such as changing the time, description, participants, or marking it as an all-day event. Practical examples include updating meeting times, adding participants to an event, or correcting event descriptions.

Properties

Name Meaning
Bucket Id The identifier of the bucket (calendar or schedule container) where the entry exists.
Entry Id The identifier of the specific schedule entry to update.
Summary A brief title or summary describing what the schedule entry is about.
Starts At The start date and time of the schedule entry in ISO 8601 format.
Ends At The end date and time of the schedule entry in ISO 8601 format.
Description Additional information about the schedule entry; supports HTML formatting.
Participant Ids A JSON array of participant IDs who will be involved in the schedule entry.
All Day Boolean flag indicating whether the event lasts all day (true) or has specific times.

Output

The node outputs JSON data representing the updated schedule entry. This typically includes the updated fields such as summary, start and end times, description, participant list, and all-day status. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the scheduling service.
  • Needs the Basecamp API base URL configured dynamically using the user's credentials.
  • Depends on the external Basecamp API to perform the update operation.

Troubleshooting

  • Invalid Bucket Id or Entry Id: If these identifiers are incorrect or do not exist, the API will likely return an error. Verify the IDs before running the node.
  • Incorrect Date Format: The Starts At and Ends At properties must be in valid ISO 8601 format. Invalid formats may cause request failures.
  • Participant Ids Parsing: The participant IDs must be provided as a valid JSON array. Malformed JSON will cause errors.
  • Authentication Errors: Ensure the API key or OAuth token is valid and has sufficient permissions to update schedule entries.
  • All Day Flag Conflicts: Setting All Day to true while providing specific start/end times might cause unexpected behavior depending on the API's handling.

Links and References

Discussion