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 manage various resources, including calendars. Specifically, the "Delete" operation for the "Calendar" resource allows users to remove a calendar by specifying its unique ID. This is useful in scenarios where obsolete or unwanted calendars need to be cleaned up programmatically within an automated workflow.
Practical examples include:
- Automatically deleting project-related calendars once a project is completed.
- Removing test or temporary calendars created during development or testing phases.
- Cleaning up user-specific calendars when a user leaves an organization.
Properties
| Name | Meaning |
|---|---|
| Calendar ID | The ID of the calendar to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details if it failed. The exact structure depends on the Scoro API response but generally includes status information and possibly metadata about the deleted calendar.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential with appropriate permissions to delete calendars.
- Requires configuration of the base URL and authentication credentials for the Scoro API within n8n.
Troubleshooting
Common issues:
- Invalid or missing Calendar ID: Ensure the Calendar ID provided exists and is correct.
- Insufficient permissions: The API key used must have rights to delete calendars.
- Network or connectivity problems: Verify that the base URL and network access to Scoro API are correctly configured.
Common error messages:
"Operation 'delete' for resource 'calendar' is not supported."— This indicates a misconfiguration or unsupported operation; verify the resource and operation names.- API errors related to authorization or invalid IDs will typically come from the Scoro API response; check credentials and input values.
Links and References
- Scoro API Documentation (for detailed API endpoints and responses)
- n8n documentation on creating custom nodes