Overview
This node integrates with a Parse Server, enabling users to perform various operations on Parse classes and objects. The "Search (Filter)" operation allows querying objects within a specified Parse class using custom filtering criteria expressed as JSON. This is useful for retrieving subsets of data based on complex conditions.
Common scenarios include:
- Retrieving records that match specific attributes or conditions.
- Filtering data for reporting or further processing in workflows.
- Paginating through large datasets by combining filters with limit and skip parameters.
For example, you might search a "Customer" class for all customers in a particular city or with a certain status.
Properties
| Name | Meaning |
|---|---|
| Class Name | The name of the Parse class to interact with (e.g., "Customer", "Order"). |
| Include | Pointer columns to expand and return full related objects instead of just references. |
| Limite | Limit the number of objects returned by the query (pagination). |
| Order | Specify a field name to sort the results by (e.g., "createdAt" or "-updatedAt"). |
| Skip | Number of objects to skip, used with limit for pagination. |
| Keys | Comma-separated list of fields to restrict the returned data to only those fields. |
| ExcludeKeys | Comma-separated list of fields to exclude from the returned data. |
| Where (String) | A JSON string representing filtering criteria to apply to the query (e.g., {"age": {"$gt": 30}}). |
Output
The node outputs an array of items where each item contains a json property with:
response: The raw response object returned by the Parse Server containing the queried data matching the filter.requestSent: The full URL of the request sent to the Parse Server API (useful for debugging).
The response typically includes an array of objects under a key like results, each representing a Parse object matching the filter criteria.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Parse Server instance.
- Needs credentials including server URL, application ID, and REST API key configured in n8n.
- Uses HTTP requests to communicate with the Parse Server REST API.
Troubleshooting
- Invalid JSON in "Where (String)": If the filter JSON is malformed, the request will fail. Ensure valid JSON syntax.
- Incorrect Class Name: Using a non-existent or misspelled class name will result in errors or empty results.
- Permission Issues: Insufficient permissions or incorrect API keys may cause authorization errors.
- Pagination Parameters: Setting
LimiteorSkipincorrectly (e.g., negative numbers) may lead to unexpected results. - Empty Results: If no objects match the filter, the response will be empty; verify filter criteria correctness.