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 creation of calendar events or tasks that have defined start and end times, participants, and descriptions. For example, you can use this node to programmatically add meetings, deadlines, or reminders to your team's shared schedule, ensuring everyone stays informed and organized.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the schedule entry will be created. |
| Schedule Id | Numeric identifier of the schedule to which the entry belongs. |
| 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 details about the schedule entry; supports HTML formatting. |
| Participant Ids | JSON array of participant IDs who will be involved in the schedule entry. |
| All Day | Boolean flag indicating if the event lasts all day (true) or has specific times (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 authentication credentials in n8n is necessary for successful API calls.
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 participant IDs that do not exist or are not accessible by the authenticated user might result in failures.
- Network or authentication issues can prevent the node from connecting to the Basecamp API.
Error Messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and valid.
- "Invalid input" or "Bad Request": Verify that required fields like Bucket Id, Schedule Id, Summary, Starts At, and Ends At are provided and correctly formatted.
- "Not Found": Ensure the specified Bucket Id and Schedule Id exist and belong to the authenticated account.
Resolving these usually involves verifying input values, ensuring proper credential setup, and confirming API access permissions.