Memberspot

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

Actions12

Overview

This node integrates with the Memberspot API to manage user-related data and actions. Specifically, for the User resource and the Set Order State operation, it allows you to update the state of a user's order by specifying their email, the order ID, and whether the order should be marked as active or inactive.

Common scenarios where this node is beneficial include:

  • Automatically updating order statuses in your membership or course platform when an order is processed, refunded, or canceled.
  • Synchronizing order states between Memberspot and other systems like CRMs or e-commerce platforms.
  • Managing access control based on order activity status.

For example, if a user completes payment for a course, you can use this node to set their order state to active, granting them access. Conversely, if a refund occurs, you can mark the order as 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 specific order to update for the user.
Active Boolean flag indicating whether the order should be set as active (true) or inactive (false).

Output

The node outputs a JSON object representing the response from the Memberspot API after attempting to set the order state. This typically includes confirmation of the updated order state or details about the affected order.

The output structure is:

{
  "json": {
    // API response fields confirming the order state update
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data 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 if "Continue On Fail" is enabled.
    • Typical error messages might include "User not found," "Order ID invalid," or "Unauthorized."

  • Resolutions:

    • Verify that 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.
    • Use the node's "Continue On Fail" option to handle errors gracefully during batch operations.

Links and References

Discussion