Parse Server icon

Parse Server

Interact with a Parse Server

Overview

This node allows interaction with a Parse Server, enabling users to perform various operations on Parse classes and objects. It supports creating, updating, deleting, retrieving by ID, searching with filters, executing cloud functions, and making custom requests to the Parse Server REST API.

Common scenarios include:

  • Managing backend data stored in Parse classes (e.g., user profiles, products).
  • Querying and filtering data with specific criteria.
  • Executing server-side logic via cloud functions.
  • Performing custom REST API calls for advanced or unsupported operations.

Practical examples:

  • Creating a new object in a "Products" class with specified attributes.
  • Retrieving a user object by its ID including related pointer objects.
  • Searching for records matching certain conditions with pagination and sorting.
  • Calling a cloud function to trigger complex business logic.
  • Sending a custom request to a specific endpoint or with custom parameters.

Properties

Name Meaning
Operation The action to perform: Create, Delete, Execute Cloud Function, Get by ID, Request Custom, Search (Filter), Update
Class Name The name of the Parse class to interact with
Object ID The ID of the Parse object to retrieve, update, or delete
Include Pointer columns to include full related objects
Limite Limit the number of objects returned by the query
Order Field name to sort the results by
Skip Number of objects to skip for pagination
Keys Restrict fields returned by the query
ExcludeKeys Fields to exclude from the returned query
Where (String) JSON string defining filtering criteria (used in search operation)
Data (String) JSON string containing data to send to Parse Server (used in create, update, customRequest, cloudFunction)
Cloud Function Name The name of the Parse Cloud Function to execute

Output

The node outputs an array of items where each item contains a json property with:

  • response: The JSON response returned by the Parse Server for the performed operation.
  • requestSent: (only for custom requests) The full URL of the request sent to the Parse Server.

If the node performs operations like create, update, get, delete, search, or cloud function execution, the response field contains the corresponding JSON data returned by the Parse Server API.

No binary data output is produced by this node.

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.
  • The node uses HTTP requests to communicate with the Parse Server REST API.

Troubleshooting

  • Invalid Credentials: If the server URL, application ID, or API key are incorrect or missing, requests will fail with authentication errors. Verify credential configuration.
  • Malformed JSON in Data or Where Fields: The data and where properties expect valid JSON strings. Invalid JSON will cause parsing errors. Use proper JSON formatting.
  • Missing Required Parameters: Operations like update, delete, and get require an Object ID. Omitting it will result in errors or unexpected behavior.
  • Unsupported Custom Requests: The custom request operation appends parsed JSON from the data field directly to the URL, which may lead to malformed URLs if not carefully constructed.
  • Pagination Parameters: The default values for limite and skip are 1, which might limit results unintentionally. Adjust these as needed.
  • Cloud Function Execution: Ensure the cloud function name is correct and that the function exists on the Parse Server.

Links and References

Discussion