Solidarity Tech

Interact with Solidarity Tech API

Actions22

Event Attendance → Get Many

AI-generated

Overview

The node interacts with the Solidarity Tech API to manage event attendance data. Specifically, for the "Event Attendance" resource and the "Get Many" operation, it retrieves multiple event attendance records from the API. This is useful in scenarios where you want to fetch attendance information for events or sessions, such as generating reports on who attended an event, syncing attendance data with other systems, or analyzing participation trends.

Practical examples:

  • Fetching all attendance records for a specific event within a date range.
  • Retrieving attendance data in batches to handle large datasets without hitting rate limits.
  • Filtering attendance records by user lists or timestamps for delta synchronization.

Properties

Name Meaning
Limit Max number of results to return (1 to 100)
Offset Number of results to skip before starting to return results
Since Unix timestamp to fetch records updated since this time (for delta sync)
User List IDs Comma-separated list of user list IDs to filter the attendance records
Enable Batch Processing Whether to enable batch processing to fetch data in chunks respecting rate limits
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; 0 means fetch all available records based on API metadata
Timeout Between Batches (Ms) Delay in milliseconds between batch requests when batch processing is enabled (100 to 30000 ms)

Output

The output is a JSON array containing event attendance records retrieved from the API. Each record typically includes details such as event ID, event session ID, user ID, and whether the user attended.

If batch processing is enabled, the node aggregates multiple pages of results into a single output array.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Solidarity Tech API.
  • The node expects a valid base URL configured in the credentials for the API endpoint.
  • Uses HTTP requests with authentication handled internally via n8n's credential system.
  • Supports batch processing with configurable batch size and timeout to respect API rate limits.

Troubleshooting

  • Missing or invalid credentials: The node will fail if the API key or base URL is missing or malformed. Ensure credentials are correctly set up.
  • Invalid base URL format: Errors occur if the base URL is not a valid HTTPS URL. Verify the URL format in credentials.
  • API rate limits exceeded: If too many requests are made quickly, the API may reject calls. Use batch processing with appropriate batch size and timeout settings to mitigate.
  • Invalid parameter values: Providing out-of-range values for limit, offset, or batch size can cause errors. Follow the specified ranges.
  • Network or HTTP errors: These will be reported with detailed debug info. Check network connectivity and API availability.
  • JSON parsing errors: Not applicable here since this operation only fetches data.

When errors occur, the node provides detailed debug information including operation type, request URLs, and timestamps to help diagnose issues.

Links and References

Discussion