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 interacts with the Scoro API to perform various operations on different resources. Specifically, for the ClientProfile resource with the Delete operation, it deletes a client profile identified by its unique ID. This is useful in scenarios where you need to programmatically remove outdated or incorrect client profiles from your Scoro account to keep your data clean and up-to-date.
Practical example: Automatically deleting client profiles that have been marked as inactive or duplicates during a data cleanup workflow.
Properties
| Name | Meaning |
|---|---|
| Client Profile ID | The unique identifier of the client profile to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any relevant status messages returned by the Scoro API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- Requires configuration of the base URL and company account ID within the credentials.
- The node depends on the Scoro API being accessible and the provided credentials having sufficient permissions to delete client profiles.
Troubleshooting
Common issues:
- Invalid or missing Client Profile ID will cause the operation to fail.
- Insufficient permissions or invalid API key may result in authentication errors.
- Network connectivity issues can prevent communication with the Scoro API.
Error messages:
"Operation 'delete' for resource 'clientProfile' is not supported."— indicates a misconfiguration or unsupported operation; verify the resource and operation names.- Authentication errors typically indicate problems with the API key or credentials setup.
- API errors related to the client profile ID usually mean the specified ID does not exist or is malformed.
To resolve these, ensure the Client Profile ID is correct, the API key credential is valid and has proper permissions, and network access to the Scoro API is available.
Links and References
- Scoro API Documentation (for detailed API endpoints and authentication)
- n8n documentation on creating custom nodes