Actions9
- Project Actions
- Task Actions
- Message Actions
- Calendar Actions
Overview
This node integrates with the Dooray API to interact with various resources including calendars. Specifically, the "Get Events" operation under the "Calendar" resource allows users to retrieve events from a specified calendar. This is useful for workflows that need to fetch and process calendar events, such as syncing events with other systems, sending reminders, or generating reports based on calendar data.
Practical examples include:
- Automatically fetching upcoming events from a team calendar to send notifications.
- Integrating calendar events into project management tools.
- Extracting event details for analytics or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Calendar ID | The ID of the calendar to query |
Output
The node outputs JSON data representing the calendar events retrieved from the specified calendar. Each item in the output typically contains details about an event such as its title, start and end times, description, attendees, and other metadata provided by the Dooray API.
If the node supports binary data (not indicated here), it would represent attachments or related files associated with calendar events, but this is not evident from the provided code snippet.
Dependencies
- Requires an API key credential for authenticating with the Dooray API.
- The base URL for API requests is
https://api.dooray.com. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Calendar ID will result in errors or empty responses.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity issues preventing access to the Dooray API endpoint.
Error messages:
- Unauthorized or 401 errors indicate problems with API credentials; verify and update the API key.
- 404 errors may mean the specified calendar does not exist or the user lacks permission.
- Rate limiting errors require waiting or adjusting request frequency.
Resolving these usually involves checking the input properties, ensuring valid credentials, and confirming API access permissions.
Links and References
- Dooray API Documentation (general reference for API endpoints and usage)
- n8n documentation on API Credentials for setting up authentication tokens