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 interact with various Scoro resources such as Users, Projects, Invoices, and more. Specifically, for the User resource with the Get operation, the node retrieves detailed information about a single user from Scoro by their unique identifier.
Common scenarios where this node is beneficial include:
- Fetching user details to display or process in workflows.
- Integrating user data from Scoro into other systems or reports.
- Automating user-related tasks based on retrieved user information.
For example, you might use this node to get a user's profile information by specifying their User ID, then use that data to update records in a CRM or send personalized 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" property supports two modes:
- From List: Search and select a user from a list fetched dynamically.
- By ID: Enter the numeric User ID directly (must be numeric).
Output
The node outputs JSON data representing the requested user's details as returned by the Scoro API. This typically includes fields such as user name, email, role, status, and other profile information relevant to the user.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Scoro API.
- Needs credentials including:
- Base URL of the Scoro instance.
- Company account identifier.
- API key for authentication.
These credentials must be configured in n8n before using the node.
Troubleshooting
Error: Operation 'get' for resource 'user' is not supported.
- This indicates an invalid combination of resource and operation was selected. Verify that "User" resource and "Get" operation are chosen correctly.
Invalid User ID format
- When entering User ID manually, ensure it is numeric only. Non-numeric input will cause validation errors.
Authentication failures
- Check that the API key and other credential details are correct and have sufficient permissions.
Empty or no user found
- If the specified user does not exist or the ID is incorrect, the API may return empty results or errors. Confirm the User ID is valid.