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 time entry records. Specifically, the "Get Many" operation under the "Time Entry" resource allows users to fetch a list of time entries with various filtering, pagination, and batching options.
Common scenarios where this node is beneficial include:
- Extracting time tracking data for reporting or analysis.
- Synchronizing time entries from Scoro into other systems.
- Automating workflows that depend on recent or filtered time entry data.
For example, a user might want to retrieve all time entries modified since the start of the year, including those deleted in the last 30 days, and process them in batches to avoid hitting API rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional parameters to customize the query: |
| - Filter | JSON object used to filter results, e.g., by modification date. |
| - Include Deleted | Boolean flag to include entries deleted within the last 30 days. |
| - Pagination | Controls how many results to return: |
| -- 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 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 JSON objects representing time entries retrieved from Scoro. Each object corresponds to a single time entry record with fields as defined by the Scoro API.
If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals solely with JSON data.
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 time entry data.
- Proper network access to Scoro's API endpoint is necessary.
Troubleshooting
- Unsupported Operation Error: If the selected operation-resource combination is not supported, the node throws an error indicating this. Ensure you select valid combinations.
- Authentication Failures: Missing or incorrect API credentials will cause authentication errors. Verify the API key and company account ID are correct.
- Invalid Filter JSON: Providing malformed JSON in the filter property can cause request failures. Validate JSON syntax before input.
- Rate Limits: Fetching large datasets without batching may hit API rate limits. Use batching options to control concurrency and intervals.
- Pagination Issues: Setting page limits too low or not handling pagination properly may result in incomplete data retrieval.