Overview
This node allows interaction with a Parse Server, a backend platform for building applications. It supports various operations such as creating, updating, deleting, retrieving, searching objects in Parse classes, executing custom requests, and running Parse Cloud Functions.
A common use case is managing application data stored in Parse Server classes—such as user profiles, posts, or other entities—directly from an n8n workflow. Another practical example is invoking server-side logic encapsulated in Parse Cloud Functions to perform complex operations or integrations.
For the "Execute Cloud Function" operation specifically, the node sends JSON data to a named Parse Cloud Function and returns its response, enabling workflows to trigger backend business logic dynamically.
Properties
| Name | Meaning |
|---|---|
| Data (String) | JSON-formatted string containing data to send to the Parse Server or Cloud Function. |
| Cloud Function Name | The name of the Parse Cloud Function to execute. |
Output
The node outputs a JSON object under the json field with the following structure:
response: Contains the parsed JSON response returned by the Parse Server after executing the cloud function.For other operations, it may also include
requestSent, which shows the full URL of the request made.
No binary data output is produced by this node.
Dependencies
- Requires access to a Parse Server instance with REST API enabled.
- Needs credentials including the server URL, application ID, and API key to authenticate requests.
- The node uses HTTP requests to communicate with the Parse Server REST API.
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 the JSON is valid.
- Authentication errors: Missing or incorrect credentials (server URL, app ID, API key) will cause authentication failures. Verify that the credentials are correctly configured.
- Cloud Function not found: If the specified cloud function name does not exist on the Parse Server, the request will fail. Confirm the function name is correct and deployed.
- Network issues: Connectivity problems to the Parse Server URL will result in request timeouts or failures. Check network accessibility and server status.