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 ClientProfile resource and the Create operation, the node enables creating a new client profile in Scoro by sending a structured JSON request body.
Common scenarios where this node is beneficial include automating client data entry workflows, syncing client information from other systems into Scoro, or programmatically managing client profiles as part of larger business process automation.
For example, a user can prepare a JSON object representing a new client’s details (such as name, contact info, and custom fields) and use this node to create that client profile directly in Scoro without manual input.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to create a client profile. This should contain all necessary fields as expected by the Scoro API for client profile creation. |
Output
The node outputs the response from the Scoro API after attempting to create the client profile. The json output field contains the API's JSON response, which typically includes details of the newly created client profile such as its unique ID and any metadata returned by Scoro.
If the API supports it, binary data output is not applicable here since this operation deals with JSON data only.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential configured in n8n with:
- Base URL of the Scoro instance.
- Company account identifier.
- API key for authentication.
- The node uses these credentials to authenticate and send requests to the Scoro REST API.
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 Property: Since the "Request" property expects a JSON object, providing invalid JSON will cause parsing errors. Ensure the JSON is well-formed.
- Authentication Failures: Incorrect or missing API credentials will result in authorization errors. Verify that the API key and company account ID are correct.
- API Errors: If the Scoro API returns validation errors (e.g., missing required fields), these will be reflected in the node’s output. Review the API response for details and adjust the request accordingly.
Links and References
- Scoro API Documentation — Official documentation for understanding the structure and requirements of client profile creation requests.
- n8n Documentation — For general guidance on using credentials and JSON parameters in n8n nodes.