Overview
This node integrates with the Calendarlink API to create calendar events within a specified organization and event collection. It is useful for automating event scheduling workflows, such as adding new meetings, appointments, or reminders directly into a calendar system managed by Calendarlink.
Typical use cases include:
- Automatically creating events from form submissions or CRM triggers.
- Scheduling follow-up meetings after sales calls.
- Organizing team events or deadlines programmatically.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The unique identifier of the organization under which the event will be created. |
| Collection ID | The identifier of the event collection (calendar) where the event should be added. |
| Title | The title or name of the event. |
| Start DateTime | The starting date and time of the event in ISO 8601 format. |
| End DateTime | The ending date and time of the event in ISO 8601 format. |
| Description | A detailed description or notes about the event. |
| Location | The physical or virtual location where the event will take place. |
| RSVP Enabled | Boolean flag indicating whether RSVP functionality is enabled for this event (true/false). |
Output
The node outputs JSON data representing the newly created event as returned by the Calendarlink API. This typically includes event details such as its unique ID, timestamps, title, description, location, RSVP status, and any other metadata provided by the API.
If the node supports binary data output (not indicated here), it would generally relate to attachments or calendar invites, but this is not evident from the static code.
Dependencies
- Requires an active connection to the Calendarlink API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://my.calendarlink.com/api/v1.
Troubleshooting
- Authentication errors: Ensure that the API key or token credential is correctly set up and has sufficient permissions.
- Invalid IDs: Verify that the Organization ID and Collection ID exist and are correct; otherwise, the API may return "not found" errors.
- Date/time format issues: Make sure the start and end datetime values are valid ISO 8601 strings and that the end time is after the start time.
- Missing required fields: All required properties must be provided; missing mandatory fields like title or dates will cause validation errors.
- API rate limits: If many events are created rapidly, you might hit API rate limits; consider adding delays or batching.
Links and References
- Calendarlink API Documentation (hypothetical link based on base URL)
- n8n documentation on creating custom nodes