Actions28
- Action Actions
- Country Actions
- Event Actions
- Language Actions
- Product Actions
- Profile Actions
- Task Actions
- Timezone Actions
- User Management Actions
- kSuite Actions
Overview
This node interacts with the Infomaniak API to manage various resources, including kSuite workspaces and mailboxes. Specifically, the Attach Mailbox operation under the kSuite resource and Workspace sub-resource allows users to attach a mailbox to the current user profile in their kSuite workspace.
Typical use cases include:
- Automating the process of linking a new mailbox to a user's kSuite account.
- Setting up mailboxes programmatically during onboarding or integration workflows.
- Managing mailbox credentials securely within automated workflows.
For example, you might use this node to attach a mailbox by providing its password and optionally marking it as the primary mailbox for the user.
Properties
| Name | Meaning |
|---|---|
| Sub Resource | Selects the kSuite sub-resource; options are: Workspace, My kSuite, Product Management. |
| Mailbox Data | Collection of fields related to the mailbox being attached: |
| - Password | The password for the mailbox (input is masked). |
| - Is Primary | Boolean flag to set this mailbox as the primary mailbox for the user. |
| Additional Options | For other sub-resources like My kSuite, allows loading additional data (not used here). |
Output
The output JSON contains the response from the Infomaniak API after attempting to attach the mailbox. On success, it returns details about the newly attached mailbox, such as mailbox identifiers and status information.
If the operation fails, an error message is returned describing the failure.
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Infomaniak API.
- The node makes HTTP requests to the Infomaniak API endpoints, specifically to
https://api.infomaniak.com/2/profile/ksuites/mailboxes. - Proper network access to Infomaniak's API is necessary.
- No additional external dependencies beyond the API key and internet connectivity.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization failures.
- Incorrect mailbox password or malformed input data may cause the API to reject the request.
- Network connectivity issues can prevent successful API calls.
Error messages:
"Failed to attach mailbox"indicates the API call did not succeed; check credentials and input parameters.- If the node throws errors related to HTTP status codes or unexpected responses, verify that the mailbox password is correct and that the user has permission to attach mailboxes.
- Validation errors on input fields (e.g., missing required password) should be checked before execution.
Resolution tips:
- Ensure the API key credential is valid and has sufficient permissions.
- Double-check the mailbox password and the "Is Primary" flag usage.
- Review network settings and firewall rules if API calls fail due to connectivity.
Links and References
- Infomaniak API Documentation (general reference for API endpoints)
- n8n Documentation for guidance on using credentials and HTTP request nodes
- Infomaniak kSuite mailbox management API endpoint:
POST /2/profile/ksuites/mailboxes(used internally by this node)
This summary focuses exclusively on the kSuite > Workspace > Attach Mailbox operation as requested.