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
Schedule Entry → Create a Schedule Entry
AI-generatedOverview
This node operation creates a new schedule entry within a specified project (bucket) and schedule in Basecamp. It is useful for automating the addition of events or appointments to a Basecamp schedule, such as meetings, deadlines, or reminders. For example, a user can create a schedule entry with a summary, start and end times, description, participant IDs, and options for all-day events and notifications.
Use Case Examples
- Create a schedule entry for a project meeting with a summary, start and end times, and notify participants.
- Add an all-day event to a schedule with detailed description and participant list.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) used in the API endpoint path, required to specify where the schedule entry will be created. |
| scheduleId | The ID of the schedule used in the API endpoint path, required to specify which schedule the entry belongs to. |
| Summary | A brief summary of what the schedule entry is about, required for describing the event. |
| Start Date/Time | The start date and time of the schedule entry in ISO 8601 format, required to define when the event begins. |
| End Date/Time | The end date and time of the schedule entry in ISO 8601 format, required to define when the event ends. |
| Description | More detailed information about the schedule entry, which may contain HTML, used to provide additional context or details. |
| Participant IDs | IDs of people participating in this schedule entry, used to specify attendees. |
| All Day Event | Boolean flag indicating whether the schedule entry should be an all-day event. |
| Send Notifications | Boolean flag indicating whether to notify participants about the entry. |
| Return Full Response | Boolean flag to determine whether to return the full API response including status code, headers, and body, instead of only the response body. |
Output
JSON
id- The unique identifier of the created schedule entry.summary- The summary text of the schedule entry.starts_at- The start date/time of the schedule entry.ends_at- The end date/time of the schedule entry.description- Detailed description of the schedule entry.participant_ids- List of participant IDs associated with the schedule entry.all_day- Indicates if the event is an all-day event.notify- Indicates if notifications were sent to participants.
Dependencies
- An API key credential for Basecamp OAuth2 authentication
Troubleshooting
- Ensure that the Project ID (bucketId) and scheduleId are correct and exist in Basecamp to avoid 404 errors.
- Verify that the date/time fields (startsAt and endsAt) are in valid ISO 8601 format to prevent validation errors.
- If notifications are enabled, ensure participant IDs are valid to avoid notification failures.
- Check API credentials and permissions if authentication errors occur.
- If the full response is requested, handle the response structure accordingly in downstream nodes.
Links
- Basecamp4 Node Documentation - Official documentation for the Basecamp4 node in n8n, including usage and examples.