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
Pages → Get All
AI-generatedOverview
The "Pages - Get All" operation in this node retrieves multiple page records from the Solidarity Tech API. It supports fetching pages with options to limit the number of results, skip a certain number of records (offset), and filter by a Unix timestamp for delta synchronization. Additionally, it can filter pages by user list IDs.
This operation is useful when you want to bulk retrieve page data for analysis, reporting, or integration purposes. For example, you might use it to synchronize all pages into a CRM system or to generate a report on recent page activity.
The node also supports batch processing to handle large datasets efficiently while respecting API rate limits by splitting requests into smaller batches with configurable size and delay between batches.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return (1 to 100). |
| Offset | Number of results to skip before starting to collect the output. |
| Since | Unix timestamp to fetch only records updated since this time (for delta sync). |
| User List IDs | Comma-separated list of user list IDs to filter the pages by associated user lists. |
| Enable Batch Processing | Boolean flag to enable batch processing mode to fetch data in multiple requests respecting rate limits. |
| Batch Size | Number of records to fetch per batch request 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 other than API meta info. |
| 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 where each element represents a page record retrieved from the API. The structure of each page object corresponds directly to the API's response schema for pages, typically including fields such as page ID, title, content, timestamps, and any metadata provided by the Solidarity Tech API.
If batch processing is enabled, the output aggregates all pages fetched across all batches into a single array.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Solidarity Tech API.
- The node expects a valid base URL for the Solidarity Tech API, which is validated and normalized internally.
- Network connectivity to the Solidarity Tech API endpoint is necessary.
Troubleshooting
- Invalid Base URL: If the base URL credential 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://).
- Authentication Failures: Errors retrieving credentials or authenticating HTTP requests will cause failures. Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate Limits / Timeouts: When fetching large datasets without batch processing, the API may throttle requests. Enabling batch processing with appropriate batch size and timeout settings can mitigate this.
- Invalid Parameter Values: Providing out-of-range values for properties like limit, offset, or batch size may cause errors. Use values within the specified ranges.
- JSON Parsing Errors: Not applicable here since this operation only performs GET requests without JSON input.
Links and References
- Solidarity Tech API Documentation (assumed based on base URL pattern)
- n8n Documentation on HTTP Request Node for understanding underlying HTTP calls
- General guidance on Batch Processing Patterns in n8n workflows