Parse Server icon

Parse Server

Interact with a Parse Server
Join our community

Actions7

Overview

This node allows interaction with a Parse Server, a backend platform for managing data objects and cloud functions. It supports various operations such as creating, retrieving by ID, updating, deleting objects, searching with filters, executing cloud functions, and making custom requests.

A common use case is integrating n8n workflows with a Parse Server backend to automate data management tasks. For example, you can retrieve a specific object by its ID to enrich workflow data, update records based on external triggers, or execute custom cloud functions to perform server-side logic.

The "Get by ID" operation specifically fetches a single object from a specified Parse class using its unique object ID, optionally including related pointer objects or filtering returned fields.

Properties

Name Meaning
Class Name The name of the Parse class (table) to interact with.
Object ID The unique identifier of the Parse object to retrieve.
Include Pointer columns to include full related objects in the response.
Limite Limit the number of objects returned by the query (note: likely a typo for "Limit").
Order Field name to sort the results by.
Skip Number of objects to skip, used for pagination.
Keys Comma-separated list of fields to restrict the returned data to.
ExcludeKeys Comma-separated list of fields to exclude from the returned data.

Output

The node outputs JSON data under the response field containing the result from the Parse Server API call. For the "Get by ID" operation, this will be the JSON representation of the requested object, including any included pointer objects or filtered fields as specified.

Additionally, the output includes the requestSent field showing the exact URL requested, useful for debugging or logging.

No binary data output is produced by this node.

Example output structure:

{
  "response": {
    "objectId": "xWMyZ4YEGZ",
    "createdAt": "2011-08-20T02:06:57.931Z",
    "updatedAt": "2011-08-20T02:06:57.931Z",
    "name": "Example Object",
    "pointerField": {
      "__type": "Pointer",
      "className": "RelatedClass",
      "objectId": "abc123"
    }
  },
  "requestSent": "https://your-parse-server.com/classes/YourClass/objectId?include=pointerField&limite=1"
}

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

  • Common issues:

    • Incorrect or missing credentials will cause authentication failures.
    • Providing an invalid or non-existent Object ID will result in errors or empty responses.
    • Typo in property names like "Limite" instead of "Limit" may cause unexpected behavior or ignored parameters.
    • Improperly formatted JSON strings in input properties (e.g., data, where) will cause parsing errors.

  • Error messages:

    • Authentication errors typically indicate invalid credentials; verify API keys and server URL.
    • 404 Not Found errors usually mean the specified object or class does not exist.
    • JSON parse errors suggest malformed JSON input; ensure all JSON strings are valid.

  • Resolution tips:

    • Double-check all input parameters for correctness.
    • Use the requestSent output to verify the constructed API request URL.
    • Validate JSON inputs with external tools before entering them into the node.

Links and References

Discussion