Actions22
- User Actions
- User Note Actions
- User Action Actions
- User Relationship Actions
- Event Actions
- Event Session Actions
- Event RSVP Actions
- Event Attendance Actions
- User List Actions
- Pages Actions
User → Get Many
AI-generatedOverview
This node integrates with the Solidarity Tech API to retrieve multiple user records ("Get Many" operation on the "User" resource). It supports fetching users with various filtering and pagination options, including batch processing to handle large datasets efficiently while respecting API rate limits.
Typical use cases include synchronizing user data from Solidarity Tech into other systems, performing bulk analysis or reporting on user information, or integrating user lists for marketing or outreach campaigns.
For example, you can fetch all users updated since a certain timestamp, limit results to a specific number per request, or process users in batches with configurable delays to avoid hitting API rate limits.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional parameters to control the query and batch processing: |
| - Limit | Max number of results to return (1-100) |
| - Offset | Number of results to skip |
| - Since | Unix timestamp to fetch only users updated since this time (delta sync) |
| - User List IDs | Comma-separated list of user list IDs to filter users |
| - Enable Batch Processing | Boolean to enable batch processing mode with timeouts |
| - Batch Size | Number of records to fetch per batch when batching is enabled (1-100) |
| - Max Records to Fetch | Maximum total number of records to fetch; 0 means no limit |
| - Timeout Between Batches (Ms) | Delay in milliseconds between batch requests when batching is enabled (100-30000 ms) |
These properties allow fine-tuning how many users are fetched, which subset to fetch, and how to paginate or batch the requests to optimize performance and comply with API constraints.
Output
The node outputs an array of JSON objects representing user records retrieved from the Solidarity Tech API. Each object corresponds to a user and contains fields as returned by the API, such as user identifiers, contact details, preferences, tags, addresses, and custom properties.
If batch processing is enabled, the output aggregates all 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 the base URL of the Solidarity Tech API to be set in the credentials.
- Uses HTTP requests with JSON payloads and responses.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
- Invalid Base URL: If the base URL in credentials is missing or malformed, the node will throw an error indicating the base URL is required or invalid. Ensure the base URL is correctly set and includes the protocol (https://).
- Credential Retrieval Failure: Errors retrieving the API key credential will cause execution failure. Verify that the API key credential exists and is accessible.
- API Rate Limits: When fetching large numbers of users without batching, you may hit API rate limits. 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 result in errors or empty results. Validate input parameters before running.
- JSON Parsing Errors: For operations involving raw JSON input (not applicable here), invalid JSON would cause parsing errors.
- Network or HTTP Errors: Any network issues or API errors will be reported with detailed debug info. Check connectivity and API status.
Links and References
- Solidarity Tech API Documentation (Assumed URL, replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General REST API Pagination Best Practices: https://swagger.io/docs/specification/2-0/pagination/