Scoro icon

Scoro

Interact with the Scoro API

Actions50

Overview

This node integrates with the Scoro API to retrieve multiple status entries. The "Get Many" operation under the "Status" resource allows users to fetch a list of status records, optionally filtered and paginated. This is useful for scenarios where you want to synchronize or analyze status data from Scoro, such as generating reports on project statuses, monitoring workflow progress, or integrating status information into other systems.

Practical examples:

  • Fetch all active statuses modified since a specific date.
  • Retrieve a limited number of statuses including those recently deleted.
  • Batch requests to efficiently handle large datasets without hitting rate limits.

Properties

Name Meaning
Options Collection of options to customize the retrieval:
- Filter JSON object 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 results or limit the number returned.
-- Page Limit Maximum number of results to return if not returning all.
- Batching Controls batching of requests 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.

Output

The node outputs an array of JSON objects representing status entries retrieved from Scoro. Each object corresponds to a single status record with fields as defined by the Scoro API's status resource schema.

If binary data were involved, it would be summarized here, 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 status 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 cause 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 'status' is not supported." — indicates a misconfiguration or unsupported operation/resource combination.
    • JSON parse errors on the Filter option — ensure valid JSON syntax.
    • API errors related to authentication — verify API key and company account ID.

  • Resolutions:

    • Double-check and re-enter API credentials.
    • Validate JSON filters using online tools before input.
    • Use batching options to manage large data requests.
    • Confirm that the selected resource and operation are correct.

Links and References

Discussion