Actions56
- API Call Actions
- Bundle Actions
- Community Actions
- Course Actions
- Group Actions
- Hub Actions
- Member Actions
- Module Actions
- Popup Actions
- Webhook Actions
Overview
The "Give Hub Access" operation in the LearningSuite node manages access permissions for a specified Hub resource. It allows users to grant or remove access rights to a Hub by specifying one or more of the following entities: Members, Groups, and Bundles. This operation is useful in scenarios where you want to control who can view or interact with content or features within a particular Hub, such as managing team collaboration spaces, course hubs, or project areas.
Practical examples include:
- Granting access to a new group of users when they join a project.
- Removing access from members who no longer should have entry to a Hub.
- Managing bundle-based access rights for licensing or subscription purposes.
Properties
| Name | Meaning |
|---|---|
| Hub Name or ID | The unique identifier or name of the Hub to which access will be granted or removed. You can select from a list or specify an ID using an expression. |
| Group Names or IDs | A list of group identifiers to grant or remove access for. Choose from available groups or specify IDs via expressions. |
| Bundle Names or IDs | A list of bundle identifiers to grant or remove access for. Select bundles from the list or specify IDs using expressions. |
| Member Names or IDs | A list of member identifiers to grant or remove access for. Select members from the list or specify IDs using expressions. |
Note: At least one of the Groups, Bundles, or Members must be selected to perform the access modification.
Output
The node outputs a JSON array containing the results of the access modification operation(s). Each item in the output corresponds to the outcome of granting or removing access for the specified entities on the given Hub. The exact structure depends on the API response but generally includes confirmation of success or details about any errors encountered.
If the operation fails for some entries but the node is set to continue on failure, error messages are included in the output alongside the input data that caused them.
No binary data output is involved in this operation.
Dependencies
- Requires a valid API authentication token credential configured in n8n to connect to the LearningSuite API.
- The node relies on LearningSuite's backend services to manage Hub access permissions.
- The node uses dynamic loading methods to populate options for Hubs, Groups, Bundles, and Members, so these lists depend on the current state of the connected LearningSuite environment.
Troubleshooting
Common Issues:
- Not selecting any Groups, Bundles, or Members will cause the operation to fail because at least one selection is required.
- Providing invalid or non-existent Hub, Group, Bundle, or Member IDs will result in errors from the API.
- Insufficient permissions in the API credentials may prevent modifying access rights.
Error Messages:
"No handler for resource "hub" and operation "addAccess"(or"removeAccess"): Indicates the node does not support the requested operation; verify the operation name.- API errors related to invalid IDs or permission issues will be passed through; check the error message for specifics.
Resolution Tips:
- Ensure all required fields are filled correctly.
- Verify that the API credentials have sufficient privileges.
- Use the option lists to select valid IDs or carefully construct expressions to provide correct values.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual errors and handle them downstream.
Links and References
- n8n Expressions Documentation
- LearningSuite API documentation (refer to your organization's internal resources or API docs provided by agentur-systeme.de)