Memberspot

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

Actions12

Overview

This node integrates with the Memberspot API to manage user-related operations, specifically allowing you to grant an offer to a user by their email address. The "Grant Offer by Email" operation is useful when you want to programmatically assign access or entitlements (offers) to users based on their email, optionally including their first and last names and associating an order ID.

Practical scenarios include:

  • Automatically granting course access or product offers to new users after registration.
  • Assigning promotional or purchased offers to existing users via automated workflows.
  • Managing user entitlements in bulk by iterating over multiple emails and offers.

Properties

Name Meaning
Email The email address of the user to whom the offer will be granted.
Offer Name or ID The specific offer to grant, selectable from a list loaded dynamically or specified by ID.
Order ID (Optional) An associated order identifier related to the offer grant.
Firstname (Optional) The user's first name, used when granting the offer.
Lastname (Optional) The user's last name, used when granting the offer.

Output

The node outputs JSON data representing the response from the Memberspot API for the grant offer request. This typically includes confirmation details about the granted offer and the user it was assigned to.

The output structure is:

{
  "json": {
    // API response object confirming the grant operation
  },
  "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 or non-existent offer IDs may result in errors from the API.
    • Providing an invalid email format could lead to request rejection.
    • Network issues or incorrect base URL configuration can cause connection errors.

  • Error messages:

    • Errors returned by the API are passed through; typical messages might indicate invalid parameters or authorization failures.
    • If the node is set to continue on fail, errors will appear in the output JSON under an error field.

  • Resolution tips:

    • Verify that the API key credential is correctly set up and has sufficient permissions.
    • Ensure the offer ID exists and is valid by using the dynamic offer list.
    • Confirm the email addresses are properly formatted.
    • Check network connectivity and the correctness of the API base URL.

Links and References

Discussion