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 to retrieve calendar events in bulk. Specifically, the "Calendar" resource with the "Get Many" operation allows users to fetch multiple calendar entries based on various filtering and pagination options.
Common scenarios where this node is beneficial include:
- Synchronizing calendar events from Scoro into another system or database.
- Generating reports or analytics on scheduled activities within a company.
- Automating workflows that depend on calendar data, such as reminders or task creation.
Practical example: A user wants to pull all calendar events modified since January 1, 2023, including those deleted in the last 30 days, and process them in batches to avoid hitting API rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional parameters to customize the query. |
| ├─ Filter | 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 to return and whether to return all or limit the number. |
| │ ├─ Return All | Whether to return all results (true) or limit the number returned (false). |
| │ └─ 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 calendar events. Each item corresponds to a calendar entry with its associated fields as provided by the Scoro API.
If binary data were involved (not indicated here), it would be summarized accordingly, but this node focuses on JSON event data.
Dependencies
- Requires an active connection to the Scoro API via an API key credential.
- The node expects credentials containing the base URL, company account ID, and API key for authentication.
- No additional external dependencies beyond the Scoro API are required.
Troubleshooting
- Unsupported Operation Error: If the selected operation-resource combination is not supported, the node throws an error indicating this. Ensure you select valid combinations.
- API Authentication Failures: Errors related to invalid or missing API keys will prevent data retrieval. Verify that the API key credential is correctly configured.
- Rate Limits: Fetching large datasets without batching may hit API rate limits. Use the batching options to control concurrency and delay between requests.
- Invalid Filter JSON: Providing malformed JSON in the filter property can cause errors. Validate JSON syntax before input.
- Pagination Misconfiguration: Setting page limits too high or conflicting with "Return All" may lead to unexpected results or performance issues.
Links and References
- Scoro API Documentation
- n8n Documentation on HTTP Request Nodes
- JSON Syntax Validator (useful for validating filter inputs)