Basecamp icon

Basecamp

Interact with the Basecamp API
Join our community

Actions68

Overview

This node updates an existing schedule entry in a Basecamp project. It allows users to modify details such as the time frame, summary, description, participants, and whether the event lasts all day. This is useful for managing and keeping schedule entries up-to-date within Basecamp directly from automated workflows.

Practical examples include:

  • Automatically adjusting meeting times or descriptions based on external calendar changes.
  • Adding or removing participants programmatically when team members change.
  • Updating event details after receiving inputs from other systems like CRM or project management tools.

Properties

Name Meaning
Bucket Id The identifier of the Basecamp project (bucket) where the schedule entry exists.
Entry Id The unique identifier of the 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 if the event lasts the entire day (true) or not (false).

Output

The node outputs JSON data representing the updated schedule entry as returned by the Basecamp API. This typically includes all the updated fields such as the entry’s ID, summary, start and end times, description, participant list, and all-day status.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the Basecamp API.
  • The node uses the Basecamp API endpoint specific to the user's Basecamp account and project (bucket).
  • Proper permissions on the Basecamp account are necessary to update schedule entries.

Troubleshooting

  • Invalid Bucket Id or Entry Id: If these identifiers are incorrect or do not exist, the API will return errors indicating the resource was not found. Verify the IDs before running the node.
  • Malformed Dates: The Starts At and Ends At properties must be valid ISO 8601 strings. Invalid formats may cause request failures.
  • Participant Ids Format: The participant IDs must be provided as a valid JSON array. Improper JSON syntax will cause parsing errors.
  • Permission Errors: Insufficient permissions or expired credentials will result in authorization errors. Ensure the API token is valid and has the required scopes.
  • All Day Flag Conflicts: Setting All Day to true while providing specific start and end times might cause unexpected behavior depending on the API's handling of these fields.

Links and References

Discussion