Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node allows you to create a new schedule entry within a specified schedule and bucket in a calendar or scheduling system. It is useful for automating the creation of events, appointments, or tasks that need to be scheduled with specific start and end times. Typical use cases include adding meetings, reminders, or any time-bound activities programmatically.
For example, you could use this node to automatically add a project deadline event to your team’s shared calendar or to schedule recurring maintenance windows without manual input.
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 description or title of 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. This typically includes details such as the entry's unique ID, summary, start and end times, description, participants, and notification status. The output can be used downstream in workflows to reference or manipulate the created schedule entry.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential or OAuth2 token configured in n8n to authenticate with the external scheduling service.
- The base URL for API requests is dynamically constructed using the authenticated account’s identifier.
- The node depends on the external scheduling system’s API being available and accessible.
Troubleshooting
- Invalid or missing required fields: Ensure that
Bucket Id,Schedule Id,Summary,Starts At, andEnds Atare provided and correctly formatted. Dates must be in valid ISO 8601 format. - Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions to create schedule entries.
- Participant IDs parsing issues: The
Participant Idsfield expects a JSON array. Invalid JSON syntax will cause errors. - Notification failures: If notifications do not reach participants, check the external service’s notification settings and participant contact information.
- API rate limits or downtime: Temporary failures may occur due to API limits or service outages; retry after some time.
Links and References
- ISO 8601 Date Format
- Documentation for the external scheduling API (not included here, but recommended to consult for detailed field descriptions and error codes)