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 update calendar entries. It allows users to modify existing calendar data by specifying the calendar ID and providing a JSON object representing the update request. This is useful for automating calendar management tasks such as changing event details, rescheduling, or adding additional information programmatically.
Practical examples include:
- Updating meeting times or descriptions in a team calendar.
- Modifying project deadlines stored in a calendar.
- Automating calendar updates based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| Calendar | Select the calendar to update. You can choose from a list of available calendars or enter a numeric calendar ID manually. |
| Request | A JSON object representing the nested update request to apply to the selected calendar. This should follow the structure expected by the Scoro API for calendar updates. |
Output
The node outputs JSON data representing the response from the Scoro API after attempting to update the calendar entry. This typically includes the updated calendar details or confirmation of the successful update.
If the API supports binary data related to calendar entries (e.g., attachments), it would be included accordingly, but this node primarily handles JSON responses.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential configured in n8n with base URL, company account ID, and API key for authentication.
- The node uses internal methods to handle API requests and responses, relying on proper credential setup.
Troubleshooting
- Invalid Calendar ID: If the calendar ID is not numeric or does not exist, the node will throw an error. Ensure the calendar ID is correct and numeric.
- Malformed JSON in Request: The "Request" property must contain valid JSON. Invalid JSON will cause parsing errors. Use a JSON validator before inputting.
- Authentication Errors: Missing or incorrect API credentials will prevent the node from connecting to Scoro. Verify that the API key and other credential details are correct.
- Unsupported Operation: If the operation or resource is not supported, the node throws an error indicating so. Confirm you are using the "update" operation on the "calendar" resource.
Links and References
- Scoro API Documentation (for detailed request/response formats)
- n8n Documentation on Creating Custom Nodes
- JSON Validators (e.g., https://jsonlint.com) for verifying the "Request" property content