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 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 identifier. This is useful in scenarios where you need to fetch and use client data within your workflows, such as generating reports, updating records, or triggering actions based on client details.
Practical examples include:
- Fetching a client profile to display or process their contact information.
- Using client profile data to customize communications or automate billing processes.
- Integrating client details into project management or CRM workflows.
Properties
| Name | Meaning |
|---|---|
| ClientProfile | The identifier of the client profile to retrieve. Can be selected from a searchable list or entered by ID (numeric only). |
The property supports two modes for specifying the client profile:
- From List: Search and select from existing client profiles.
- By ID: Enter the numeric ID of the client profile directly.
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.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential configured in n8n with appropriate permissions to access client profiles.
- The base URL and authentication details are taken from the configured credentials.
Troubleshooting
- Operation Not Supported Error: If you receive an error stating the operation is not supported, verify that the resource is set to "ClientProfile" and the operation to "Get".
- Invalid Client Profile ID: When entering the ID manually, ensure it is numeric; otherwise, validation will fail.
- Authentication Issues: Ensure the API key and other credential details are correct and have sufficient permissions.
- Empty or Missing Data: If no client profile is returned, confirm the ID exists in Scoro and that the user has access rights.
Links and References
- Scoro API Documentation
- n8n Documentation on Creating Custom Nodes