Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node integrates with the Scoro API to interact with various resources, including calendars. Specifically, the "Get" operation for the "Calendar" resource allows users to retrieve details about a specific calendar by selecting it from a list or providing its ID directly. This is useful in scenarios where you want to fetch calendar information such as events or metadata for scheduling, reporting, or synchronization purposes.
Practical examples include:
- Fetching a calendar's details before creating or updating events.
- Retrieving calendar data to display in custom dashboards.
- Integrating calendar information into workflows that manage tasks or projects.
Properties
| Name | Meaning |
|---|---|
| Calendar | The calendar to retrieve. Can be selected from a searchable list of available calendars or specified by its unique ID. |
Output
The node outputs JSON data representing the calendar details retrieved from the Scoro API. This typically includes fields such as calendar ID, name, description, and other relevant metadata depending on the API response. There is no indication that binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- Needs configuration of the base URL and company account ID within the credentials.
- The node depends on the Scoro API being accessible and the provided credentials having sufficient permissions to read calendar data.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect calendar ID or selecting a non-existent calendar from the list will result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Operation 'get' for resource 'calendar' is not supported."— This indicates a misconfiguration or unsupported operation; ensure the resource and operation names are correct.- Authentication errors usually indicate invalid API keys or insufficient permissions; verify credentials.
- If the calendar cannot be found, check that the calendar ID is correct or that the calendar exists in the connected Scoro account.
Links and References
- Scoro API Documentation (for detailed API endpoints and data structures)
- n8n documentation on creating custom nodes