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 you to create a single participant for a calendar event within the connected service. It is useful when you want to programmatically add attendees or organizers to an event, specifying their role and response status. Typical use cases include automating event management workflows such as inviting team members, setting up meetings with clients, or managing event participants dynamically based on other triggers or data sources.
For example, you could use this node to add a new participant as an organizer or attendee to a scheduled meeting, specify their response status (e.g., accepted or tentative), and control how much related information is returned about the participant and event.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines the level of nested related objects included in the response: 0 returns only the primary object; 1 includes directly related objects; 2 includes related objects of those related objects. |
| Person Id | The unique identifier of the person to be added as a participant. |
| Display Name | The display name of the participant. |
| Is Organizer | Boolean flag indicating if the participant is the organizer of the event (true or false). |
| Calendar Event Id | The unique identifier of the calendar event to which the participant will be added. |
| Response Status | The participant's response status to the event invitation. Options are: NEEDS ACTION, DECLINED, TENTATIVE, ACCEPTED. |
| Handle | A handle or username associated with the participant. |
| Workspace Member Id | The unique identifier of the workspace member to be added as a participant. |
Output
The output JSON contains the created calendar event participant object. The structure reflects the participant's details including identifiers, display name, role (organizer or not), response status, and potentially nested related objects depending on the "Depth" property setting.
If binary data were supported, it would typically represent attachments or media related to the participant or event, but this operation focuses on JSON data representing participant metadata.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external calendar service.
- The node uses a base URL and headers preset for JSON communication with the API.
- No additional external dependencies beyond the configured API credentials and network access to the calendar service.
Troubleshooting
- Missing or invalid IDs: Ensure that the
personId,calendarEventId, andworkspaceMemberId(if used) are valid and exist in the target system. - Authentication errors: Verify that the API key or authentication token is correctly set up and has sufficient permissions to create event participants.
- Invalid response status: Use one of the allowed options (
NEEDS_ACTION,DECLINED,TENTATIVE,ACCEPTED) for the response status to avoid validation errors. - API rate limits or connectivity issues: Check network connectivity and API usage limits if requests fail intermittently.
- Incorrect depth value: Use only 0, 1, or 2 for the depth parameter to ensure proper response formatting.
Links and References
- Refer to the official API documentation of the calendar service for detailed information on participant creation and response status meanings.
- n8n documentation on creating custom nodes and using API credentials for authentication.