Overview
This node allows interaction with a Parse Server, a backend platform for building applications with a flexible data model. It supports various operations such as creating, updating, deleting, retrieving, searching objects in Parse classes, executing cloud functions, and making custom requests.
Common scenarios include:
- Creating new records in a specified Parse class.
- Updating or deleting existing records by their object ID.
- Retrieving single or multiple records with filtering, sorting, and pagination.
- Executing server-side cloud functions to perform custom logic.
- Performing advanced queries or custom REST requests on the Parse Server.
Practical example: You can use this node to create a new user profile in a "User" class by providing JSON data representing the user's details, or to search for all active orders in an "Order" class using a filter query.
Properties
| Name | Meaning |
|---|---|
| Class Name | The name of the Parse class to interact with (e.g., "User", "Order"). |
| Data (String) | JSON-formatted string containing the data to send to the Parse Server for create/update operations. |
Output
The node outputs a JSON object under the json field with the following structure:
response: The response returned from the Parse Server API call, typically containing the created/updated/deleted object data or query results.requestSent(only for some operations like customRequest): The full URL of the request sent to the Parse Server.
If binary data were involved, it would be summarized here, but this node only handles JSON data exchanges.
Dependencies
- Requires connection credentials to a Parse Server instance, including:
- Server URL
- Application ID
- REST API Key or equivalent API authentication token
- These credentials must be configured in n8n prior to using the node.
Troubleshooting
- Invalid JSON in Data property: If the JSON string provided in the "Data (String)" property is malformed, the node will throw a parsing error. Ensure valid JSON syntax.
- Missing or incorrect credentials: Authentication errors may occur if the server URL, application ID, or API key are missing or incorrect. Verify credential configuration.
- Object ID required for update/delete/get operations: Operations that require an object ID will fail if it is not provided or invalid.
- Network or server errors: Check connectivity to the Parse Server and ensure the server is running and accessible.
- Incorrect class name or cloud function name: Using a non-existent class or cloud function will result in errors from the Parse Server.