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 invoice records based on specified criteria. The "Get Many" operation for the Invoice resource allows users to fetch a list of invoices, 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 invoice data from Scoro into another system or database.
- Generating reports or dashboards that require up-to-date invoice information.
- Automating workflows that depend on recent or specific subsets of invoices.
Practical example:
- Fetch all invoices modified since January 1, 2023, excluding those deleted in the last 30 days, returning results in batches of pages to avoid hitting rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings to customize the retrieval of invoices: |
| - Filter | A JSON object used to filter the invoices returned. For example, filtering by modified_date to get invoices changed after a certain date. |
| - Include Deleted | Boolean flag indicating whether to include invoices that have been deleted within the last 30 days. |
| - Pagination | Controls how many invoices to return and whether to return all available results or limit the number: |
| -- Return All | Whether to return all matching invoices or only up to a specified limit. |
| -- Page Limit | Maximum number of invoices to return if not returning all. |
| - Batching | Settings to control concurrent requests and pacing to avoid rate limits: |
| -- Pages per Batch | Number of pages requested concurrently in each batch. |
| -- Batch Interval (ms) | Time in milliseconds to wait between each batch of requests. |
Output
The node outputs an array of JSON objects representing invoices retrieved from Scoro. Each object contains invoice details as provided by the Scoro API, such as invoice ID, dates, amounts, client information, and status.
If binary data were involved (e.g., invoice PDFs), it would be included in a separate binary property, but this operation focuses on JSON data output.
Dependencies
Requires an active connection to the Scoro API using valid credentials, including:
- Base URL of the Scoro instance.
- Company account identifier.
- API key for authentication.
The node expects these credentials to be configured in n8n prior to execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted JSON in the Filter property may result in parsing errors.
- Requesting too many pages without batching might lead to rate limiting by the Scoro API.
Error messages:
"Operation 'getAll' for resource 'invoice' is not supported."indicates a misconfiguration or unsupported operation/resource combination.- JSON parse errors when providing the Filter option can be resolved by ensuring valid JSON syntax.
- Rate limit errors can be mitigated by adjusting batching options (reducing pages per batch or increasing batch interval).