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 interacts with the Scoro API to retrieve multiple company records based on specified criteria. The "Get Many" operation under the "Company" resource allows users to fetch a list of companies, optionally filtered by certain conditions, including deleted entries, and supports pagination and batching for efficient data retrieval.
Common scenarios where this node is beneficial include:
- Synchronizing company data from Scoro into another system.
- Generating reports or dashboards that require up-to-date company information.
- Automating workflows that depend on bulk company data extraction.
For example, a user might want to retrieve all companies modified since the start of the year, including those recently deleted, and process them in batches to avoid hitting API rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional parameters to customize the data retrieval: |
| - Filter | A JSON object used to filter the results. For example, filtering companies modified after a specific date. |
| - Include Deleted | Boolean flag indicating whether to include companies deleted in the last 30 days. |
| - Pagination | Controls how many results to return and whether to return all results or limit the number: |
| -- Return All | Whether to return all matching results or only up to a specified limit. |
| -- Page Limit | Maximum number of results to return if not returning all. |
| - Batching | Settings to control concurrent requests and pacing to avoid rate limits: |
| -- Pages per Batch | Number of pages to request concurrently in each batch. |
| -- Batch Interval (ms) | Time in milliseconds to wait between each batch of requests. |
Output
The node outputs an array of company objects in the json field of the output items. Each object represents a company record retrieved from Scoro, containing fields as defined by the Scoro API's company resource schema.
If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals solely with JSON data representing company entities.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- Needs the base URL and company account ID configured in the credentials.
- The node uses the Scoro API endpoints to fetch company data.
- Proper network access to Scoro's API endpoint is necessary.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted JSON in the Filter property can lead to parsing errors.
- Requesting too many pages without batching may hit API rate limits.
- Including deleted entries when none exist may return empty results.
Error Messages:
"Operation 'getAll' for resource 'company' is not supported."— This indicates a misconfiguration or unsupported operation; verify the selected resource and operation.- JSON parse errors for the Filter option — Ensure the JSON syntax is correct.
- API authentication errors — Check that the API key and other credentials are valid and have sufficient permissions.
Links and References
- Scoro API Documentation — Official API reference for understanding available endpoints and data structures.
- n8n Documentation — General guidance on using n8n nodes and handling credentials.
- JSON formatting tools — Useful for validating the Filter JSON input before use.