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, allowing users to perform various operations on different Scoro resources such as tasks, projects, clients, and more. Specifically, for the Task - Create operation, it enables creating a new task in Scoro by sending a JSON-formatted request body that defines the task details.
Common scenarios where this node is beneficial include automating task creation from other systems or workflows, syncing tasks between platforms, or programmatically managing project tasks without manual entry.
For example, you could use this node to create a task whenever a new issue is logged in a bug tracker, or to generate follow-up tasks automatically after a meeting is scheduled.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to create a new task in Scoro. |
The "Request" property expects a JSON structure that matches the Scoro API's requirements for creating a task. This allows full flexibility to specify all relevant task fields supported by the API.
Output
The node outputs the response from the Scoro API after attempting to create the task. The output is structured as JSON data containing the details of the created task or error information if the creation failed.
If the API returns any binary data (not typical for task creation), it would be included accordingly, but this operation primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Scoro API.
- Needs credentials including:
- Base URL of the Scoro instance.
- Company account identifier.
- An API key for authentication.
- These credentials must be configured in n8n before using the node.
Troubleshooting
- Unsupported Operation Error: If you select an operation-resource combination not implemented, the node throws an error indicating the operation is unsupported.
- Invalid JSON in Request: The "Request" property requires valid JSON. Malformed JSON will cause parsing errors. Ensure the JSON is well-formed.
- Authentication Failures: Incorrect or missing API credentials will result in authorization errors. Verify the API key and company account ID are correct.
- API Errors: If the Scoro API rejects the request due to invalid fields or business logic, the node will return the error message from the API. Review the request payload against Scoro’s API documentation.