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 Calendar Channel Event Association object by its unique identifier. It allows modifying various fields related to the association between calendar channels and events, such as linking to recurring events or specifying external event IDs.
Common scenarios include:
- Synchronizing calendar event associations when event details change.
- Updating references to recurring events or external event identifiers.
- Adjusting which calendar channel an event is associated with.
For example, if you have an event linked to a specific calendar channel and need to update its external ID or associate it with a different recurring event, this operation facilitates that update.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the Calendar Channel Event Association object to update. This is required. |
| Depth | Determines how much nested related data to return in the response: - 0: Only the primary object's information. - 1: Primary object plus directly related objects. - 2: Primary object, directly related objects, and their related objects. |
| Recurring Event External Id | The external ID of the recurring event to associate with this calendar channel event association. |
| Calendar Event Id | The ID of the calendar event to link to this association. |
| Calendar Channel Id | The ID of the calendar channel to link to this association. |
| Event External Id | The external ID of the event. |
Output
The node outputs the updated Calendar Channel Event Association object in JSON format. The structure includes the updated fields and, depending on the Depth parameter, may include nested related objects up to two levels deep.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the underlying service.
- The base URL for the API is configured via credentials.
- The node uses HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Missing or invalid Id: The operation requires a valid object ID; ensure the "Id" property is correctly set.
- Invalid depth value: Only 0, 1, or 2 are accepted; other values may cause errors or unexpected results.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or connectivity issues: Ensure the n8n instance can reach the API endpoint.
- Invalid field values: For example, incorrect external IDs or non-existent calendar channel/event IDs may cause the update to fail.
Links and References
- Refer to the API documentation of the calendar service for detailed schema and field descriptions.
- n8n documentation on creating and using custom nodes with API integrations.