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 perform various operations on different resources. Specifically, for the Calendar - Create operation, it allows users to create new calendar events in their Scoro account by sending a structured JSON request representing the event details.
Common scenarios where this node is beneficial include:
- Automating event creation based on triggers or workflows.
- Synchronizing external calendar data into Scoro.
- Programmatically managing schedules and appointments within business processes.
For example, a user could automate creating project meetings or deadlines as calendar events whenever a new project task is assigned.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body for creating a calendar event in Scoro. This should contain all necessary event details formatted according to Scoro's API specification. |
Output
The node outputs JSON data representing the response from the Scoro API after attempting to create the calendar event. This typically includes details of the newly created event such as its ID, timestamps, and any other metadata returned by the API.
If the API supports returning binary data (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON.
Dependencies
- Requires an active connection to the Scoro API via an API key credential.
- The node expects credentials that provide:
- Base URL of the Scoro instance.
- Company account identifier.
- API key for authentication.
- No additional environment variables are required beyond these credentials.
Troubleshooting
- Unsupported Operation Error: If you select an operation-resource combination not implemented, the node will throw an error indicating the operation is unsupported.
- Invalid JSON in Request: Since the "Request" property expects a JSON object, malformed JSON input will cause parsing errors. Ensure the JSON is valid and correctly structured.
- Authentication Failures: Incorrect or missing API credentials will result in authorization errors from the Scoro API. Verify that the API key and company account ID are correct.
- API Errors: If the Scoro API returns errors (e.g., missing required fields in the request), these will be surfaced in the node’s output. Review the API documentation to ensure the request body meets all requirements.
Links and References
- Scoro API Documentation — Official API docs for understanding the structure of calendar event requests and responses.
- n8n Documentation — For general guidance on using n8n nodes and handling JSON inputs.