Scoro icon

Scoro

Interact with the Scoro API

Actions46

Overview

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

Common scenarios include:

  • Extracting all tasks modified after a certain date for reporting or synchronization.
  • Retrieving active and recently deleted tasks for audit purposes.
  • Fetching tasks in manageable batches to avoid hitting API rate limits.

Practical example:

  • A project manager wants to pull all tasks updated since the start of the year, including those deleted within the last 30 days, to update an external dashboard.

Properties

Name Meaning
Options Collection of options to customize the retrieval of tasks.
├─ Filter JSON object used to filter results, e.g., by modification date or other task attributes.
├─ Include Deleted Boolean flag indicating whether to include tasks deleted in the last 30 days.
├─ Pagination Controls how many results to return and whether to return all or limit the number of tasks fetched.
│ ├─ Return All Whether to fetch all matching tasks or only up to a specified limit.
│ └─ Page Limit Maximum number of tasks to return if not returning all.
└─ Batching Settings to control concurrent requests and delay between batches to manage API rate limits.
├─ Pages per Batch Number of pages requested concurrently in each batch.
└─ Batch Interval (ms) Milliseconds to wait between each batch of requests.

Output

The node outputs an array of task objects in the json field of the output data. Each object represents a single task with its properties as returned by the Scoro API.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation focuses on JSON task data.

Dependencies

  • Requires connection to the Scoro API via an API key credential.
  • Needs configuration of base URL and company account ID as part of the credentials.
  • The node uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Unsupported Operation Error: If the selected resource-operation combination is not supported, the node throws an error specifying the unsupported operation. Ensure "Task" resource and "Get Many" operation are selected.
  • Invalid Filter JSON: Providing malformed JSON in the filter option will cause parsing errors. Validate JSON syntax before input.
  • API Rate Limits: Fetching large datasets without batching may hit API rate limits. Use batching options to control concurrency and intervals.
  • Include Deleted Flag Misuse: Setting "Include Deleted" incorrectly might result in unexpected data. Confirm if deleted tasks are needed.
  • Credential Issues: Missing or incorrect API key or base URL will cause authentication failures. Verify credentials setup.

Links and References

Discussion