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 within a membership or course platform. Specifically, the "Set Offer State" operation allows you to activate or deactivate a particular offer for a user identified by their email address. This is useful in scenarios where you want to control user access to specific offers dynamically, such as enabling a promotional offer, suspending access temporarily, or revoking an offer after expiration.

Practical examples:

  • Activating a special discount offer for a user who has just qualified.
  • Deactivating an offer when a user's subscription lapses.
  • Managing trial offers by toggling their active state based on user behavior.

Properties

Name Meaning
Email The email address of the user whose offer state you want to set.
Offer Name or ID The identifier or name of the offer to be activated or deactivated for the user.
Active Boolean flag indicating whether the offer 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 offer state. This typically includes confirmation of the updated state or details about the user-offer relationship. The output is paired with the input item index for traceability.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "json": {
    "email": "user@example.com",
    "offerId": "12345",
    "active": true,
    "message": "Offer state updated successfully"
  },
  "pairedItem": {
    "item": 0
  }
}

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: The node will fail to authenticate with the Memberspot API.
    • Incorrect email or offer ID: The API may return errors if the user or offer does not exist.
    • Network errors or timeouts: Connectivity issues can cause request failures.

  • Error messages:

    • "Failed to load offers": Indicates problems fetching available offers, possibly due to authentication or network issues.
    • API error responses are passed through; typical errors include "User not found" or "Offer not found".

  • Resolutions:

    • Verify that the API key credential is correctly set up and valid.
    • Ensure the email and offer ID values correspond to existing records in Memberspot.
    • Check network connectivity and firewall settings.
    • Use the "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion