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 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 results, e.g., by modification date. |
| - Include Deleted | Boolean flag to include entries deleted in the last 30 days. |
| Pagination | Controls how many results are returned: |
| - Return All | Whether to return all results or limit the number of results. |
| - 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 an array of JSON objects representing the retrieved trigger entries from Scoro. Each object corresponds to a single trigger record as returned by the Scoro API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to triggers, but this is not specified in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- Needs configuration of the base URL and company account ID as part of the credentials.
- The node uses the Scoro API endpoints to fetch trigger data.
- No additional external dependencies beyond the Scoro API and n8n's credential system.
Troubleshooting
- Unsupported Operation Error: If the node throws an error like
Operation 'getAll' for resource 'trigger' is not supported, ensure that the Resource is set to "Trigger" and Operation to "Get Many" (internally "getAll"). - API Authentication Issues: Errors related to authentication usually mean the API key or base URL is incorrect or missing. Verify the configured credentials.
- Rate Limits: If the node fails due to rate limiting, adjust the batching options to reduce concurrent requests or increase the batch interval.
- Invalid Filter JSON: Providing malformed JSON in the Filter option will cause parsing errors. Ensure the filter JSON is valid.
- Empty Results: If no data is returned, check the filter criteria and whether "Include Deleted" is set appropriately.
Links and References
- Scoro API Documentation
- n8n Documentation on Creating Nodes
- JSON Syntax Validator (useful for validating filter JSON input)