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. Specifically, for the ClientProfile - Get operation, it retrieves detailed information about a single client profile from Scoro based on a provided client profile ID. This is useful in scenarios where you need to fetch and use client data within your workflows, such as generating reports, updating CRM systems, or triggering follow-up actions based on client details.
Practical examples:
- Fetching a client profile to display their contact information in a dashboard.
- Retrieving client details before creating an invoice or project associated with that client.
- Using client profile data to personalize communications or automate marketing workflows.
Properties
| Name | Meaning |
|---|---|
| ClientProfile | The client profile to retrieve. You can select it either from a searchable list of profiles or specify the client profile ID directly (must be numeric). |
The property supports two modes:
- From List: Search and select a client profile from existing profiles.
- By ID: Enter the numeric ID of the client profile manually.
Output
The node outputs JSON data representing the client profile retrieved from Scoro. This typically includes all available fields related to the client profile such as name, contact details, company info, and any custom fields defined in Scoro.
If the node supports binary data output, it would be used to represent files or attachments related to the client profile, but this is not indicated in the provided code snippet.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential configured in n8n with the base URL and authentication details for Scoro.
- The node uses internal methods to handle API requests and list searching, relying on the credentials and resource-operation routing defined in the bundled code.
Troubleshooting
Common issues:
- Providing a non-numeric client profile ID when using the "By ID" mode will cause validation errors.
- Missing or incorrect API credentials will result in authentication failures.
- Selecting an unsupported operation or resource combination will throw an error indicating the operation is not supported.
Error messages:
"Operation 'get' for resource 'clientProfile' is not supported."— This means the requested operation-resource pair is invalid or not implemented.- Validation error
"User ID must be numeric"— Occurs if the client profile ID does not match the required numeric format. - Authentication errors due to missing or invalid API keys should be resolved by verifying the configured credentials.
Links and References
- Scoro API Documentation (for understanding available endpoints and data structures)
- n8n Documentation on Creating Custom Nodes