Actions50
- Status Actions
- Task Actions
- Calendar Actions
- ClientProfile Actions
- Comment Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node interacts with the Scoro API to perform various operations on different resources. Specifically, for the Calendar - Get operation, it retrieves details of a specific calendar by its identifier. This is useful in scenarios where you want to fetch calendar information such as events or metadata from Scoro within an automated workflow.
Practical examples include:
- Automatically fetching calendar details to synchronize with other calendar services.
- Retrieving calendar data to display or process in downstream workflow steps.
- Using calendar information to trigger notifications or updates based on scheduled events.
Properties
| Name | Meaning |
|---|---|
| Calendar | The calendar to retrieve. Can be selected either from a searchable list of calendars or specified directly by its ID. |
The "Calendar" property supports two modes:
- From List: Select a calendar from a searchable list fetched dynamically.
- By ID: Provide the calendar's unique identifier as a string.
Output
The node outputs JSON data representing the calendar details retrieved from the Scoro API. This typically includes fields such as calendar name, description, events, and other metadata depending on the API response.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the calendar, but this is not applicable for the "Get" operation on the calendar resource.
Dependencies
- Requires an active connection to the Scoro API using valid credentials including:
- Base URL of the Scoro instance.
- Company account identifier.
- API key for authentication.
These credentials must be configured in n8n prior to using the node.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation-resource combination, the node will throw an error indicating the operation is not supported. Ensure you select "Get" operation under the "Calendar" resource.
- Authentication Errors: Invalid or missing API credentials will cause authentication failures. Verify that the API key and company account ID are correctly set.
- Invalid Calendar ID: Providing a non-existent or incorrect calendar ID will result in an error or empty response. Use the "From List" mode to select valid calendars if unsure.
- Network Issues: Connectivity problems with the Scoro API endpoint can cause request failures. Check network access and base URL configuration.
Links and References
- Scoro API Documentation – Official API reference for detailed information on calendar endpoints and data structures.
- n8n Documentation – General guidance on configuring credentials and using nodes in workflows.