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 integrates with the Scoro API to perform various operations on different resources, including calendar events. Specifically, for the Calendar resource with the Create operation, it allows users to create new calendar events by sending a structured JSON request body representing the event details.
Common scenarios where this node is beneficial include automating event creation in Scoro based on triggers or workflows in n8n, such as scheduling meetings, deadlines, or reminders programmatically without manual input.
Practical example:
- Automatically create a calendar event in Scoro when a new task is assigned in a project management tool.
- Schedule recurring meetings by generating calendar events from external data sources.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to create a calendar event. This should contain all necessary fields as per Scoro's API specification for calendar events. |
Output
The node outputs JSON data representing the response from the Scoro API after creating the calendar event. This typically includes details of the newly created event such as its ID, title, start and end times, and other metadata returned by the API.
If the API supports binary data (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON.
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 properly configured to accept requests.
Troubleshooting
- Unsupported Operation Error: If you select an operation not supported for the Calendar resource, the node will throw an error indicating the operation is unsupported. Ensure you use only valid operations like "create" for the Calendar resource.
- Invalid JSON in Request Property: Since the Request property expects a JSON object, providing invalid JSON will cause parsing errors. Make sure the JSON is well-formed.
- Authentication Failures: Errors related to authentication usually mean the API key or base URL is incorrect or missing. Verify your credentials are correctly set up.
- API Response Errors: If the Scoro API returns errors (e.g., validation errors for the event data), these will be passed through. Check the request body conforms to Scoro's API requirements.
Links and References
- Scoro API Documentation — For detailed information on calendar event creation and required JSON structure.
- n8n Documentation — For general guidance on using custom nodes and handling JSON inputs.