Scoro icon

Scoro

Interact with the Scoro API

Actions46

Overview

This node integrates with the Scoro API to retrieve multiple project records based on user-defined criteria. It is designed to fetch many projects at once, supporting filtering, pagination, and batching to efficiently handle large datasets.

Common scenarios include:

  • Synchronizing project data from Scoro into another system.
  • Generating reports or dashboards that require bulk project information.
  • Automating workflows that depend on up-to-date project lists filtered by modification date or other attributes.

For example, a user might want to get all projects 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 Collection of options to customize the retrieval:
- Filter A JSON object used to filter results, e.g., by modification date.
- Include Deleted Boolean flag to include projects deleted within the last 30 days.
- Pagination Controls how many results to return:
-- Return All Whether to return all matching projects or limit the number of results.
-- Page Limit Maximum number of projects 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 of requests.

Output

The node outputs an array of project objects in the json field of each item. Each object represents a project retrieved from Scoro, containing its properties as returned by the API.

If batching is used, the output will be a combined list of all projects fetched across batches.

No binary data output is produced by this operation.

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 project data.
  • Proper network access to Scoro's API endpoint is necessary.

Troubleshooting

  • Unsupported Operation Error: If the node throws an error stating the operation is not supported, verify that "Get Many" is selected under the "Project" resource.
  • Authentication Failures: Ensure the API key and other credential details are correct and have sufficient permissions.
  • Rate Limits: If requests fail due to rate limiting, adjust batching options to reduce concurrent requests or increase batch intervals.
  • Invalid Filter JSON: When using the filter option, ensure the JSON syntax is valid; otherwise, the API may reject the request.
  • Empty Results: Confirm that the filter criteria match existing projects and that "Include Deleted" is set appropriately if expecting deleted entries.

Links and References

Discussion