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 creating multiple calendar event participants in bulk. It is useful when you need to add several participants to a calendar event at once, such as inviting a group of people to a meeting or event programmatically. Instead of adding participants one by one, this operation streamlines the process by accepting an array of participant data and sending it in a single request.
Practical examples include:
- Automatically inviting all team members to a scheduled project meeting.
- Adding attendees to a webinar event based on a registration list.
- Syncing participants from another system into your calendar events.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary calendar event participant objects.- 1: Primary objects plus their directly related objects.- 2: Primary objects, their related objects, and those related objects' related objects. |
| Body | JSON object representing the calendar event participants to create. This should be a JSON array or object specifying participant details. The default example includes a "responseStatus": "NEEDS_ACTION" field indicating the participant's status. |
Output
The output contains a JSON structure representing the created calendar event participants. Depending on the depth parameter, the response may include nested related objects up to two levels deep. This typically includes participant details and potentially linked entities such as user profiles or event metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the external calendar service.
- The node uses a base URL configured via credentials to connect to the calendar API.
- The operation sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the "Body" property is malformed, the request will fail. Ensure the JSON syntax is correct before executing.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly set up in the node credentials.
- Depth Parameter Misuse: Setting an unsupported depth value may result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
- API Rate Limits: Creating many participants at once might hit API rate limits. If you encounter rate limit errors, consider batching requests or adding delays.
Links and References
- Refer to your calendar service’s API documentation for detailed schema of calendar event participants and supported fields.
- JSON formatting tools can help validate the "Body" input before use.