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 Action → Get Many
AI-generatedOverview
The node interacts with the Solidarity Tech API to perform operations related to "User Action" resources. Specifically, for the "Get Many" operation, it retrieves multiple user action records from the API. This is useful in scenarios where you want to fetch a list of user actions for analysis, reporting, or further processing within an automation workflow.
For example, you might use this node to:
- Retrieve recent user actions filtered by time or user lists.
- Fetch large datasets of user actions using batch processing to handle API rate limits efficiently.
- Integrate user action data into other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional parameters to control the query and pagination: |
| - Limit | Maximum number of results to return (1 to 100). |
| - Offset | Number of results to skip before starting to collect the result set. |
| - Since | Unix timestamp to filter results for delta synchronization (only actions since this time). |
| - User List IDs | Comma-separated list of user list IDs to filter the user actions by specific user lists. |
| - Enable Batch Processing | Boolean flag to enable batch processing mode, which fetches 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 across all batches (0 means no limit, fetch all available). |
| - Timeout Between Batches (Ms) | Delay in milliseconds between batch requests to avoid hitting rate limits (100 to 30000 ms). |
Output
The output is a JSON array containing user action objects retrieved from the Solidarity Tech API. Each object represents a user action record with fields as defined by the API's response schema.
If batch processing is enabled, the node aggregates results from multiple paginated requests 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 the base URL of the API to be configured in the credentials.
- Uses internal HTTP request helpers with authentication to communicate with the API.
- Supports batch processing with configurable batch size and timeout to respect API rate limits.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect or malformed base URL in credentials can lead to URL validation errors.
- Exceeding API rate limits if batch processing is disabled or improperly configured.
- Invalid parameter values (e.g., negative limit or offset) may cause API errors.
Error Messages:
- Failed to get credentials: Indicates missing or misconfigured API key credential.
- Base URL is required but not provided in credentials: Credentials lack the necessary API base URL.
- Invalid base URL format: The base URL does not conform to expected URL syntax.
- HTTP Request Error: General failure during API call; check network connectivity, credentials, and parameters.
- Invalid JSON in userDataJson: If using raw JSON input elsewhere, indicates malformed JSON string.
Resolutions:
- Verify that the API key credential is correctly set up in n8n.
- Ensure the base URL is properly formatted and includes protocol (https://).
- Use batch processing options to avoid hitting rate limits on large data fetches.
- Validate input parameters for correctness and completeness.
Links and References
- Solidarity Tech API Documentation (Assumed based on context)
- n8n Documentation on Creating Custom Nodes
- General info on Handling API Pagination and Rate Limits
Note: The above summary is based solely on static code analysis of the provided source code and property definitions.