Memberspot

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

Actions12

Overview

The node integrates with the Memberspot API to manage and retrieve user-related data within an online course or membership platform. Specifically, the "List Users" operation fetches a paginated list of users, optionally filtered by their active status, associated course ID, or offer ID.

This node is useful for scenarios such as:

  • Retrieving all users enrolled in a specific course or offer.
  • Filtering users based on whether they are currently active or inactive.
  • Paginating through large user lists to process or analyze user data incrementally.

For example, you could use this node to generate reports on active users in a particular course or to synchronize user data with another system.

Properties

Name Meaning
Additional Options A collection of optional filters and pagination controls:
- Active Filter Filter users by status: All, Active Only, or Inactive Only
- Filter by Course ID Filter users enrolled in a specific course by providing its ID
- Filter by Offer Name or ID Filter users associated with a specific offer, selectable from a list or via expression
- Last Loaded ID Identifier for pagination to continue loading from a specific page (from previous response)
- Page Length Number of users to return per page (pagination size)

Output

The node outputs JSON data containing the list of users retrieved from the Memberspot API. The structure typically includes user details such as IDs, names, emails, and other relevant metadata depending on the API response.

If pagination is used, the output may also include a next_page property indicating the identifier to be used for subsequent requests.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Memberspot API.
  • The node expects the base URL of the Memberspot API to be configured in the credentials.
  • Network access to the Memberspot API endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key will cause authentication failures.
    • Incorrect base URL configuration can lead to connection errors.
    • Using invalid filter values (e.g., non-existent course or offer IDs) may result in empty responses or errors.
    • Pagination parameters must be correctly managed to avoid repeated or skipped data.

  • Error Messages:

    • Errors returned from the API are captured and presented; typical messages include authentication errors, invalid parameters, or rate limiting.
    • If the node is set to continue on failure, errors for individual items will be included in the output JSON under an error field.

  • Resolution Tips:

    • Verify API key and base URL in credentials.
    • Confirm that filter values correspond to existing courses or offers.
    • Use the Last Loaded ID parameter properly to paginate through results.
    • Enable "Continue On Fail" cautiously to handle partial failures gracefully.

Links and References

Discussion