Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node interacts with the Scoro API, specifically supporting a "Trigger" resource with a "Get Many" operation. It is designed to retrieve multiple trigger entries from Scoro, allowing users to filter results, include recently deleted entries, and control pagination and batching of requests.
Common scenarios where this node is beneficial include:
- Automating workflows that need to react to or process multiple triggers from Scoro.
- Synchronizing trigger data from Scoro into other systems.
- Performing bulk data retrieval for reporting or analysis purposes.
For example, a user might configure this node to fetch all triggers modified since a certain date, including those deleted in the last 30 days, and process them in batches to avoid hitting API rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of options to customize the retrieval: |
| - Filter | A JSON object used to filter the results, e.g., by modification date. |
| - Include Deleted | Boolean flag indicating whether 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 each batch of requests. |
Output
The node outputs JSON data representing the retrieved trigger entries from Scoro. Each item in the output corresponds to a trigger record matching the specified filters and options.
If the node supports binary data output, it would typically represent attachments or files related to triggers; however, based on the provided code and properties, the output focuses on JSON data only.
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 trigger data.
- No additional external dependencies are indicated.
Troubleshooting
- Unsupported Operation Error: If the node throws an error like
Operation 'getAll' for resource 'trigger' is not supported, ensure that the resource and operation names are correctly set to "Trigger" and "Get Many" respectively. - API Authentication Issues: Errors related to authentication usually mean the API key or base URL is incorrect or missing. Verify the credentials configuration.
- Rate Limiting: If the node fails due to too many requests, adjust the batching options to reduce concurrency or increase the batch interval.
- Invalid Filter JSON: Providing malformed JSON in the filter property will cause parsing errors. Ensure the filter JSON is valid.
Links and References
- Scoro API Documentation
- n8n documentation on Creating Custom Nodes