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, retrieving, updating, deleting objects in Parse classes, executing cloud functions, performing custom requests, and searching/filtering data.
The Delete operation specifically deletes an object from a specified Parse class by its Object ID. This is useful when you want to remove records or entries from your Parse database programmatically within an n8n workflow.
Practical example:
You have a user management system where users can be deleted based on certain conditions. Using this node's Delete operation, you can automate the removal of user records from the Parse Server by specifying the class (e.g., "User") and the Object ID of the user to delete.
Properties
| Name | Meaning |
|---|---|
| Class Name | The name of the Parse class to interact with (e.g., "User", "Product"). |
| Object ID | The unique identifier of the Parse object to delete. Required to specify which object to remove. |
Output
The output JSON contains a response field that holds the server's response to the delete request. Typically, for a successful delete operation, this will be an empty object {} indicating the object was removed.
Example output JSON:
{
"response": {}
}
No binary data is output by this node.
Dependencies
- Requires connection credentials to a Parse Server instance, including:
- Server URL
- Application ID
- REST API Key
These must be configured in n8n as credentials and linked to the node.
- The node uses HTTP requests to communicate with the Parse Server REST API.
Troubleshooting
- Missing Object ID: If the Object ID is not provided, the delete operation cannot target any object, resulting in an error or no action.
- Invalid Class Name or Object ID: If either the class name or object ID does not exist on the Parse Server, the API will return an error indicating the object was not found.
- Authentication errors: Ensure the API key and application ID are correct; otherwise, the server will reject the request.
- Network issues: Verify the server URL is reachable from the n8n environment.
Common error messages may include:
"Object not found": The specified object ID does not exist in the given class."Unauthorized"or"Invalid API key": Credentials are incorrect or missing."Malformed JSON": Input data is not properly formatted JSON (relevant for other operations).
To resolve these, double-check input parameters, credentials, and network connectivity.