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 within a Scoro account. Specifically, for the User - Get operation, it retrieves detailed information about a single user by their unique numeric ID. This is useful in scenarios where you need to fetch user details such as profile information, roles, or permissions for further processing or automation workflows.
Practical examples include:
- Fetching user details to personalize task assignments.
- Retrieving user info to synchronize with other HR or CRM systems.
- Validating user existence before performing updates or notifications.
Properties
| Name | Meaning |
|---|---|
| User | Select the user to retrieve. You can either pick from a searchable list of users or enter a numeric User ID manually. The User ID must be numeric. |
Output
The node outputs JSON data representing the user object retrieved from the Scoro API. This typically includes fields such as user ID, name, email, role, and other profile-related information depending on the API response structure.
If the node supports binary data output (not indicated here), it would represent any files or attachments related to the user, but this operation primarily returns JSON data.
Dependencies
- Requires an active connection to the Scoro API via an API key credential.
- The node expects configuration of the base URL and authentication credentials for the Scoro API.
- No additional external services are required beyond the Scoro API.
Troubleshooting
Error: Operation 'get' for resource 'user' is not supported.
This indicates that the requested operation-resource combination is invalid or not implemented. Verify that "User" resource and "Get" operation are correctly selected.Validation error on User ID:
If entering the User ID manually, ensure it is numeric only. Non-numeric input will cause validation failure.Authentication errors:
Ensure the API key and base URL credentials are correctly configured and have sufficient permissions to access user data.Empty or no user found:
If the specified User ID does not exist, the API may return an empty result or error. Confirm the User ID is correct and exists in the Scoro account.
Links and References
- Scoro API Documentation – Official API docs for understanding user data structure and available endpoints.
- n8n Documentation on Creating Custom Nodes – For extending or troubleshooting custom node implementations.