Memberspot

Interact with the Memberspot API (powered by agentur-systeme.de)

Actions12

Overview

The node integrates with the Memberspot API to manage user-related data and actions. Specifically, for the User resource and Set Order State operation, it allows updating the state (active or inactive) of a specific order associated with a user identified by their email address.

This is useful in scenarios where you need to programmatically activate or deactivate orders for users, such as managing access to purchased content, subscriptions, or services within a learning platform or membership system powered by Memberspot.

Practical example:
You have an automation that processes payment confirmations. When a payment is confirmed, this node can be used to set the corresponding order state to active, granting the user access to the purchased offer. Conversely, if a refund occurs, the order state can be set to inactive to revoke access.

Properties

Name Meaning
Email The email address of the user whose order state you want to update.
Order ID The identifier of the order for which the state will be set.
Active Boolean flag indicating whether the order should be active (true) or inactive (false).

Output

The node outputs JSON data representing the response from the Memberspot API after attempting to set the order state. This typically includes confirmation details about the updated order state or error information if the request failed.

The output structure is:

{
  "json": {
    // Response object from Memberspot API related to the order state update
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Memberspot API.
  • The node expects the Memberspot API base URL and API key to be configured in the credentials.
  • Network connectivity to the Memberspot API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect email or order ID may result in errors or no changes applied.
    • Network issues or incorrect base URL configuration can lead to request failures.

  • Error messages:

    • Errors returned from the API are passed through and included in the node's output when "Continue On Fail" is enabled.
    • Typical errors include "User not found", "Order not found", or "Unauthorized".

  • Resolution tips:

    • Verify the API key credential is correctly set up and has sufficient permissions.
    • Double-check the email and order ID values for correctness.
    • Ensure the Memberspot API base URL is accurate and reachable.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion