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 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:
- Synchronizing task data from Scoro into other systems.
- Generating reports or dashboards that require bulk task information.
- Automating workflows that depend on up-to-date task lists filtered by specific conditions (e.g., modified date).
Practical example:
- Retrieve all tasks modified since January 1, 2023, excluding deleted ones, and process them in batches of 20 pages with a 1-second interval between batches to avoid hitting rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of options to customize the retrieval of tasks. |
| ├─ Filter | A JSON object used to filter results, e.g., by modified date or other task attributes. |
| ├─ Include Deleted | Boolean flag indicating whether to include tasks deleted within the last 30 days. |
| ├─ Pagination | Controls how many results to return and whether to return all results or limit the number. |
| │ ├─ Return All | Whether to return all matching tasks or only up to a specified limit. |
| │ └─ Page Limit | Maximum number of tasks to return if not returning all. |
| └─ Batching | Settings for batch processing to manage concurrent requests and avoid rate limits. |
| ├─ Pages per Batch | Number of pages requested concurrently in each batch. |
| └─ Batch Interval (ms) | Time in 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 task retrieved from Scoro, containing its properties as returned by the 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 using an API key credential.
- Needs configuration of base URL and company account ID via credentials.
- The node handles API request headers and authentication internally.
Troubleshooting
- Unsupported Operation Error: If the selected operation-resource combination is not supported, the node throws an error indicating this. Ensure "Task" resource and "Get Many" operation are selected.
- API Authentication Issues: Errors related to invalid or missing API keys will prevent data retrieval. Verify that the API key and company account ID are correctly configured.
- Rate Limits: When retrieving large datasets, hitting API rate limits may cause failures. Use batching options to control concurrency and intervals between requests.
- Invalid Filter JSON: Providing malformed JSON in the filter option can cause parsing errors. Validate JSON syntax before input.
Links and References
- Scoro API Documentation — Official API reference for understanding available endpoints and parameters.
- n8n Documentation — For general guidance on creating and using custom nodes and handling credentials.