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 updates a single participant of a calendar event. It allows modifying details such as the participant's identity, display name, organizer status, response status, and related identifiers. This is useful in scenarios where you need to programmatically manage event attendees, for example, updating a participant’s RSVP status, changing the organizer, or correcting participant information in an automated workflow.
Practical examples:
- Automatically marking a participant as accepted or declined based on external triggers.
- Changing the organizer of a calendar event participant dynamically.
- Updating participant details when syncing with another calendar system.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the calendar event participant to update (required). |
| Depth | Level of nested related objects to include in the response: 0 (primary object only), 1 (primary + direct relations), 2 (including relations of related objects). |
| Person Id | Identifier of the person associated with the participant. |
| Display Name | The display name of the participant. |
| Is Organizer | Boolean flag indicating if this participant is the organizer of the event. |
| Calendar Event Id | Identifier of the calendar event to which the participant belongs. |
| Response Status | Participant's response status; options are NEEDS ACTION, DECLINED, TENTATIVE, ACCEPTED. |
| Handle | A handle or username associated with the participant. |
| Workspace Member Id | Identifier linking the participant to a workspace member. |
Output
The node outputs JSON data representing the updated calendar event participant object. The structure includes the participant’s updated fields and may include nested related objects depending on the Depth property setting. No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate requests to the underlying calendar service API.
- The node uses HTTP requests with JSON payloads to interact with the calendar event participants endpoint.
- Proper configuration of the API base URL and authentication credentials in n8n is necessary.
Troubleshooting
- Missing or invalid Id: The update operation requires a valid participant Id. Ensure the Id is provided and correct.
- Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Invalid response status value: Use one of the allowed options (NEEDS_ACTION, DECLINED, TENTATIVE, ACCEPTED).
- API rate limits or network issues: May cause request failures; check connectivity and API usage quotas.
- Incorrect depth value: Should be 0, 1, or 2; other values might cause unexpected responses.
Links and References
- Refer to the calendar service API documentation for detailed schema and behavior of calendar event participants.
- n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.