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 retrieve multiple company records based on specified criteria. It is designed to fetch a list of companies, optionally filtered by certain conditions, and supports pagination and batching to efficiently handle large datasets.
Common scenarios where this node is beneficial include:
- Synchronizing company data from Scoro into another system.
- Generating reports or analytics based on company information.
- Automating workflows that require bulk access to company details.
For example, you might use this node to get all companies modified after January 1, 2023, including those deleted in the last 30 days, and process them in batches to avoid hitting API rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of options to customize the retrieval: |
| - Filter | A JSON object used to filter results, e.g., by modification date. |
| - Include Deleted | Boolean flag to include entries deleted in the last 30 days. |
| Pagination | Controls how many results are returned: |
| - Return All | Whether to return all matching results or limit the number. |
| - Page Limit | Maximum number of results to return if not returning all. |
| Batching | Controls batch request behavior to manage rate limits: |
| - Pages per Batch | Number of pages requested concurrently in each batch. |
| - Batch Interval (ms) | Time in milliseconds to wait between batches. |
Output
The node outputs an array of company objects in the json field of each item. Each object contains company details as returned by the Scoro API, such as company name, ID, contact information, and other metadata.
If batching is used, the output will be a combined list of all retrieved companies across batches.
No binary data is output by this node.
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 REST API endpoints to fetch company data.
Troubleshooting
- Unsupported Operation Error: If you select an operation-resource combination not implemented, the node throws an error indicating the operation is unsupported. Ensure you select "Get Many" under the "Company" resource.
- Invalid Filter JSON: Providing malformed JSON in the filter option can cause parsing errors. Validate your JSON syntax before input.
- API Rate Limits: Fetching large datasets without batching may hit API rate limits. Use the batching options to control concurrency and intervals.
- Authentication Failures: Incorrect or missing API credentials will prevent successful requests. Verify your API key and base URL settings.
Links and References
- Scoro API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)
- JSON Validator tools (e.g., https://jsonlint.com/) for validating filter inputs