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
This node allows you to create a new schedule entry within a specified schedule and bucket in Basecamp. It is useful for automating the addition of events or appointments to your team's shared calendar, ensuring everyone stays informed about upcoming activities. For example, you can use this node to programmatically add meetings, deadlines, or reminders with detailed descriptions and participant notifications.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket where the schedule entry will be created (number). |
| Schedule Id | The identifier of the schedule to which the entry belongs (number). |
| Summary | A brief title or summary describing what the schedule entry is about (string). |
| Starts At | The start date and time of the schedule entry in ISO 8601 format (string). |
| Ends At | The end date and time of the schedule entry in ISO 8601 format (string). |
| Description | Additional information about the schedule entry; supports HTML formatting (string). |
| Participant Ids | JSON array of participant IDs who will be involved in the event (array of numbers/strings). |
| All Day | Boolean flag indicating if the event lasts all day (true/false). |
| Notify | Boolean flag indicating whether participants should be notified about the entry. |
Output
The node outputs JSON data representing the newly created schedule entry as returned by the Basecamp API. This typically includes details such as the entry's unique ID, timestamps, summary, description, participants, and other metadata confirming successful creation.
No binary data output is produced by this node.
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 for successful operation.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id or Schedule Id may cause the API request to fail.
- Incorrectly formatted ISO 8601 dates for "Starts At" or "Ends At" can lead to errors.
- Providing invalid participant IDs or malformed JSON in the Participant Ids field may result in rejection.
- Lack of proper API credentials or expired tokens will prevent the node from authenticating.
Error Messages:
- Authentication errors usually indicate issues with the API key or OAuth token; re-authenticate or update credentials.
- Validation errors from the API often specify which required fields are missing or incorrectly formatted.
- Network or connectivity errors suggest checking internet access or Basecamp service status.