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 retrieve multiple client profiles based on specified criteria. The "Get Many" operation under the "ClientProfile" resource allows users to fetch a list of client profiles, optionally filtered by various parameters, including modification date and deletion status. It supports pagination and batching to efficiently handle large datasets.
Common scenarios where this node is beneficial include:
- Synchronizing client profile data from Scoro into another system.
- Generating reports or analytics based on client profiles.
- Automating workflows that require up-to-date client information.
Practical example:
- Fetch all client profiles modified since January 1, 2023, excluding those deleted in the last 30 days, retrieving results in batches of 20 pages with a 1-second interval between batches to avoid rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of options to customize the retrieval of client profiles: |
| - Filter | A JSON object used to filter results, e.g., filtering by modification date. Example: {"modified_date": {"from_date": "2023-01-01"}} |
| - Include Deleted | Boolean flag indicating whether to include entries deleted in the last 30 days (true) or exclude them (false). |
| - Pagination | Controls how many results to return: |
| -- Return All | Whether to return all matching results (true) or limit the number of results (false). |
| -- Page Limit | Maximum number of results to return when not returning all (minimum 1, default 50). |
| - Batching | Controls batch request behavior to manage rate limits: |
| -- Pages per Batch | Number of pages requested concurrently in each batch (minimum 1, default 20). |
| -- Batch Interval (ms) | Time in milliseconds to wait between each batch of requests (minimum 0, default 1000 ms). |
Output
The node outputs an array of client profile objects in the json field of the output data. Each object represents a client profile retrieved from Scoro, containing fields as defined by the Scoro API for client profiles (e.g., name, contact details, modification dates).
If batching or pagination is used, the output aggregates all fetched pages into a single array.
No binary data output is produced by this operation.
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 Scoro.
- No additional external dependencies beyond the Scoro API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted JSON in the Filter option may cause parsing errors.
- Requesting too many pages without batching may hit API rate limits.
Error messages:
"Operation 'getAll' for resource 'clientProfile' is not supported."— indicates a misconfiguration or unsupported operation; verify resource and operation names.- JSON parse errors for the Filter property — ensure valid JSON syntax.
- API errors related to authentication or permissions — check API key validity and access rights.
Resolutions:
- Validate and re-enter API credentials.
- Use the batching options to reduce request frequency.
- Test filter JSON separately to confirm correctness.