Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation allows users to create multiple calendar events in bulk. It is useful when you need to add many events at once to a calendar system, such as scheduling a series of meetings, appointments, or reminders programmatically. For example, an event planner could use this to upload all events for a conference schedule in one go, or a team manager could batch-create recurring team meetings.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary event data. - 1: Primary event plus directly related objects. - 2: Primary event, related objects, and their related objects. |
| Body | JSON object representing the calendar events to create. This includes details like conference links with labels and URLs. The JSON must be valid and structured according to the calendar event schema expected by the API. |
Output
The output json field contains the response from the calendar API after creating the events. It will include the created event objects with fields depending on the selected depth level, potentially including nested related objects. If binary data were involved (not indicated here), it would represent attachments or media related to the events.
Dependencies
- Requires an API key credential for authenticating requests to the external calendar service.
- The node uses a base URL configured via credentials to connect to the calendar API.
- The request expects JSON content type and returns JSON responses.
Troubleshooting
- Invalid JSON in Body: If the "Body" property contains malformed JSON, the node will fail. Ensure the JSON is correctly formatted.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly set up in n8n credentials.
- API Limits or Quotas: Creating many events at once might hit rate limits imposed by the calendar service. Consider batching smaller numbers if errors occur.
- Depth Parameter Misuse: Setting an unsupported depth value may result in unexpected responses or errors. Use only 0, 1, or 2 as defined.
Links and References
- Refer to your calendar service's API documentation for the exact structure of event objects and supported fields.
- JSON formatting guides can help ensure the "Body" input is valid.
- n8n documentation on using credentials and HTTP request nodes for further customization.