Scoro icon

Scoro

Interact with the Scoro API

Actions46

Overview

This node integrates with the Scoro API to retrieve multiple status entries ("Get Many" operation on the "Status" resource). It is designed to fetch a list of statuses from Scoro, optionally filtered by criteria such as modification date, including deleted entries, and supports pagination and batching to handle large datasets efficiently.

Common scenarios include:

  • Synchronizing status data from Scoro into another system.
  • Reporting or analytics where you need to process all or filtered statuses.
  • Automating workflows that depend on up-to-date status information.

For example, you could use this node to get all statuses modified since the start of the year, including those recently deleted, and process them in batches to avoid hitting API rate limits.

Properties

Name Meaning
Options A collection of options to customize the retrieval:
- Filter JSON object to filter results, e.g., by modified date.
- Include Deleted Boolean flag to include entries deleted in the last 30 days.
- Pagination Controls how many results to return:
-- 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 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 the retrieved status entries from Scoro. Each object corresponds to a single status record with fields as defined by the Scoro API for statuses.

If binary data were involved, it would be summarized here, but this operation deals only 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 the Scoro API endpoint is necessary.

Troubleshooting

  • Unsupported Operation Error: If the operation or resource is not supported, the node throws an error indicating so. Ensure you select the correct resource ("Status") and operation ("Get Many").
  • Authentication Failures: Missing or invalid API credentials will cause authentication errors. Verify that the API key, base URL, and company account ID are correctly set.
  • Rate Limits: Fetching large datasets without batching may hit API rate limits. Use the batching options to control concurrency and delay between requests.
  • Invalid Filter JSON: Providing malformed JSON in the filter option will cause parsing errors. Ensure the filter JSON is valid.
  • Empty Results: If no statuses match the filter criteria, the output will be empty. Adjust filters accordingly.

Links and References

Discussion