LearningSuite icon

LearningSuite

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

Actions56

Overview

This node interacts with the LearningSuite API to retrieve multiple member records in bulk. The "Get Many" operation under the "Member" resource fetches a list of members, supporting pagination and filtering based on login activity.

Common scenarios where this node is useful include:

  • Exporting or syncing member data for reporting or analysis.
  • Filtering members who have been inactive for a certain number of days.
  • Retrieving member groups along with member details for segmentation or targeted communication.

Practical example:

  • A training administrator wants to get all members who have not logged in for at least 7 days to send them reminder emails. They can set the "Days Not Logged In (GTE)" filter to 7 and optionally exclude members who never logged in.

Properties

Name Meaning
Limit Max number of member results to return (minimum 1). Default is 50.
Offset Number of member results to skip for pagination (minimum 0). Default is 0.
Include Groups Whether to include group information for each member in the response (true/false).
Days Not Logged In (GTE) Filter members who have not logged in for at least this many days (1 to 365). Default is 7.
Include Never Logged In Whether to include members who have never logged in (true/false). Default is true.

Output

The node outputs an array of JSON objects representing members. Each object contains member details as returned by the LearningSuite API, potentially including:

  • Member identification fields (e.g., ID, name, email).
  • Login activity metadata.
  • Group information if "Include Groups" is enabled.

If group information is included, it will be nested within each member's data.

The node does not output binary data.

Dependencies

  • Requires a valid API key credential for the LearningSuite API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the LearningSuite API being accessible and responsive.

Troubleshooting

  • No handler for resource and operation: This error occurs if the node configuration specifies a resource-operation combination that is not implemented. Ensure "Member" resource and "Get Many" operation are selected correctly.
  • API authentication errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify credentials and endpoint settings.
  • Pagination issues: Setting very high limits may cause timeouts or large responses. Use reasonable limits and offsets.
  • Filtering parameters invalid: Ensure "Days Not Logged In (GTE)" is between 1 and 365; otherwise, the API may reject the request.
  • Empty results: Could indicate no members match the filters or offset exceeds available data.

Links and References

Discussion