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
The node interacts with the Scoro API to retrieve multiple time entry records. Specifically, the "Get Many" operation under the "Time Entry" resource fetches a list of time entries based on optional filtering, pagination, and batching parameters.
This node is useful for scenarios where you need to extract time tracking data from Scoro for reporting, analysis, or integration with other systems. For example, you might want to pull all time entries modified after a certain date, include recently deleted entries, or control how many results are returned per request to manage performance and rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of options to customize the retrieval of time entries: |
| - Filter | JSON object used to filter results, e.g., by modification date or other criteria. |
| - Include Deleted | Boolean flag to include entries deleted in the last 30 days. |
| - Pagination | Controls result pagination: |
| -- Return All | Whether to return all matching results or limit the number returned. |
| -- Page Limit | Maximum number of results to return if not returning all. |
| - Batching | Controls batch request behavior to avoid rate limits: |
| -- Pages per Batch | Number of pages requested concurrently in each batch. |
| -- Batch Interval (ms) | Time in milliseconds to wait between batches of requests. |
Output
The node outputs an array of time entry objects in the json field of the output items. Each object represents a single time entry record retrieved from Scoro, containing fields as defined by the Scoro API for time entries (e.g., timestamps, user info, project/task references, duration).
No binary data output is produced by this operation.
Dependencies
- Requires connection to the Scoro API via an API key credential.
- The node expects the base URL and authentication details to be configured in the credentials.
- No additional external dependencies beyond the Scoro API and n8n's HTTP request capabilities.
Troubleshooting
- Unsupported Operation Error: If the node throws an error stating the operation is not supported, verify that the selected resource is "Time Entry" and the operation is "Get Many" (internally "getAll").
- API Authentication Errors: Ensure the API key and base URL are correctly set in the credentials; invalid or missing credentials will cause authentication failures.
- Filter JSON Parsing Issues: When providing a filter, ensure the JSON syntax is valid; malformed JSON will cause errors when parsing the filter parameter.
- Rate Limits: If requests fail due to rate limiting, adjust batching options to reduce concurrent requests or increase batch intervals.
- Pagination Limits: If too few results are returned, check pagination settings—either enable "Return All" or increase the page limit.
Links and References
- Scoro API Documentation — Official API docs for understanding available fields and filters for time entries.
- n8n Documentation — General guidance on using n8n nodes and configuring credentials.