Memberspot

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

Actions12

Overview

The node integrates with the Memberspot API to manage user-related data and actions. Specifically, for the User resource and the Set Custom Properties operation, it allows setting or updating custom properties for a user identified by their email address.

This is useful in scenarios where you want to enrich user profiles with additional metadata or attributes that are not part of the standard user fields. For example, you might want to store preferences, subscription details, or any other custom information relevant to your business logic.

Practical example: After a user completes a survey, you could use this node to update their profile with custom properties reflecting their answers, enabling personalized marketing or content delivery.

Properties

Name Meaning
Email The email address of the user whose custom properties you want to set or update.
Custom Properties A collection of key-value pairs representing the custom properties to assign to the user. Each property has:
- ID: The identifier/name of the custom property.
- Value: The value to assign to that property.

Output

  • The output JSON contains the response from the Memberspot API after attempting to set the custom properties.
  • The structure depends on the API's response but generally includes confirmation of the updated properties or error details if the operation failed.
  • No binary data is output by this operation.

Example output snippet (conceptual):

{
  "success": true,
  "updatedProperties": [
    {
      "id": "property1",
      "value": "value1"
    },
    {
      "id": "property2",
      "value": "value2"
    }
  ]
}

Dependencies

  • Requires an API key credential for the Memberspot API.
  • The node makes HTTP requests to the Memberspot API base URL configured in the credentials.
  • Proper network access to the Memberspot API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect email format or non-existent user email may result in errors or no updates.
    • Providing empty or malformed custom properties can lead to API rejection.

  • Error messages:

    • Errors returned by the API are passed through; typical messages might include "User not found" or "Invalid property ID".
    • Network or timeout errors may occur if the API is unreachable.

  • Resolutions:

    • Verify the API key credential is correctly configured and active.
    • Ensure the email corresponds to an existing user in Memberspot.
    • Validate the custom properties IDs and values before sending.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion