Solidarity Tech

Interact with Solidarity Tech API

Actions22

Event → Get Many

AI-generated

Overview

The "Get Many" operation for the "Event" resource in this node allows users to retrieve multiple event records from the Solidarity Tech API. It supports fetching events with options such as limiting the number of results, skipping a certain number of records (offset), filtering by a timestamp for delta synchronization, and applying user list filters. Additionally, it supports batch processing to handle large datasets efficiently while respecting API rate limits.

This operation is beneficial when you want to:

  • Synchronize or import a list of events into your workflow.
  • Retrieve events updated since a specific time for incremental updates.
  • Handle large volumes of event data by batching requests to avoid hitting API limits.

Practical examples include:

  • Importing all upcoming events into a CRM system.
  • Fetching events created or updated after a certain date for reporting.
  • Processing events in batches to update an external calendar or notification system.

Properties

Name Meaning
Options Collection of optional parameters to control the retrieval behavior:
- Limit Maximum number of event records to return (1 to 100).
- Offset Number of event records to skip before starting to return results.
- Since Unix timestamp to fetch only events updated since this time (for delta sync).
- User List IDs Comma-separated list of user list IDs to filter events by associated user lists.
- Enable Batch Processing Boolean flag to enable batch processing mode, which fetches data in chunks with delays between batches.
- Batch Size Number of records to fetch per batch when batch processing is enabled (1 to 100).
- Max Records to Fetch Maximum total number of records to fetch across all batches (0 means no limit, fetch all available).
- Timeout Between Batches (Ms) Delay in milliseconds between batch requests to respect API rate limits (100 to 30000 ms).

Output

The output is a JSON array where each element represents an event object retrieved from the API. The structure of each event object corresponds to the API's event data schema, typically including fields such as event ID, name, description, start and end times, location details, and other metadata.

If batch processing is enabled, the output aggregates all fetched batches into a single array.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n for authenticating with the Solidarity Tech API.
  • The node expects a valid base URL for the API endpoint, provided via credentials.
  • Network connectivity to the Solidarity Tech API is necessary.
  • Optional batch processing respects API rate limits by introducing configurable delays.

Troubleshooting

  • Missing or invalid credentials: The node will fail if the API key or base URL is not properly configured. Ensure credentials are set up correctly.
  • Invalid base URL format: If the base URL does not start with http:// or https://, the node attempts to prepend https://. If the URL remains invalid, an error is thrown.
  • API rate limits exceeded: When fetching large datasets without batch processing, the API may throttle requests. Enable batch processing with appropriate batch size and timeout settings to mitigate this.
  • Invalid parameter values: Providing out-of-range values for limit, offset, or timestamps may cause errors or unexpected results.
  • Network issues: Connectivity problems can cause HTTP request failures; verify network access to the API endpoint.
  • JSON parsing errors: Not applicable here since this operation only performs GET requests without user-provided JSON input.

Links and References

Discussion