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, allowing users to perform various operations on different Scoro resources. Specifically, for the Task resource and the Create operation, it enables creating new tasks in a Scoro account by sending a JSON-formatted request body that defines the task details.
Common scenarios where this node is beneficial include automating task creation workflows, integrating task management into broader business processes, or syncing tasks from other systems into Scoro.
For example, a user might use this node to automatically create a task when a new project milestone is reached or when a client submits a request through a form.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to create a task in Scoro. This should contain all necessary fields as per Scoro's API specification for task creation. |
Output
The node outputs JSON data representing the response from the Scoro API after creating the task. This typically includes details of the newly created task such as its ID, status, timestamps, and any other metadata returned by the API.
If the API supports binary data in responses (not indicated here), the node would handle it accordingly, but based on the provided code and properties, output is JSON only.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential along with base URL and company account ID configured in n8n credentials for authentication.
- The node uses these credentials to authenticate requests to Scoro’s REST API endpoints.
Troubleshooting
- Unsupported Operation Error: If you select an operation-resource combination not implemented (e.g., "create" for a resource other than those supported), the node will throw an error indicating the operation is not supported.
- Invalid JSON in Request Property: Since the "Request" property expects a JSON string that is parsed before sending, invalid JSON syntax will cause parsing errors. Ensure the JSON is well-formed.
- Authentication Failures: Incorrect or missing API credentials will result in authorization errors from the Scoro API. Verify that the API key, base URL, and company account ID are correctly set in the node credentials.
- API Errors: Any errors returned by the Scoro API (such as validation errors on task creation) will be passed through. Review the API response message for details.
Links and References
- Scoro API Documentation — For detailed information on the task creation endpoint and required request structure.
- n8n Documentation — For guidance on setting up credentials and using custom nodes.