Memberspot

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

Actions12

Overview

This node integrates with the Memberspot API to manage user data and related resources. Specifically, the "Delete Users" operation under the "User" resource allows you to delete multiple users by specifying their email addresses. This is useful for automating user management tasks such as removing inactive or unwanted users from your system.

Practical examples:

  • Automatically deleting users who have unsubscribed or whose accounts need to be purged.
  • Bulk removal of test or temporary users after a campaign or event.
  • Cleaning up user lists based on external triggers or workflows.

Properties

Name Meaning
Emails Comma-separated list of email addresses of users to delete (e.g., user1@example.com,user2@example.com).

Output

The output is a JSON object representing the response from the Memberspot API after attempting to delete the specified users. It typically contains information about the success or failure of the deletion request.

If an error occurs during the operation, the output will contain an error field with the error message.

No binary data is produced by this operation.

Example output structure:

{
  "success": true,
  "deletedEmails": [
    "user1@example.com",
    "user2@example.com"
  ]
}

or in case of error:

{
  "error": "Error message describing what went wrong"
}

Dependencies

  • Requires an API key credential for authenticating with 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.
    • Incorrectly formatted emails (e.g., missing commas or invalid email syntax) may cause the API to reject the request.
    • Network connectivity problems can prevent successful API calls.

  • Common error messages:

    • "Unauthorized" or similar indicates invalid API credentials; verify and update the API key.
    • "Bad Request" or validation errors usually mean the emails parameter is malformed; ensure emails are comma-separated and valid.
    • "Unknown error" may indicate unexpected issues; check network and API status.

  • Resolution tips:

    • Double-check the API key and its permissions.
    • Validate the emails string format before running the node.
    • Enable "Continue On Fail" option if you want the workflow to proceed despite individual errors.

Links and References

Discussion