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 user profiles and related sub-resources. Specifically, for the Profile resource and the Get Application Password operation, it retrieves details of a specific application password by its unique identifier.
Use cases include:
- Fetching details about a particular application password associated with a user's profile.
- Managing security credentials programmatically within workflows that integrate with Infomaniak services.
- Automating audits or checks on application passwords without manual API calls.
Example: You want to retrieve information about an application password used by a third-party app connected to your Infomaniak account to verify its status or permissions.
Properties
| Name | Meaning |
|---|---|
| Password ID | The unique identifier (number) of the application password you want to retrieve details for. |
Output
The node outputs JSON data representing the requested application password's details as returned by the Infomaniak API. This typically includes fields such as the password's ID, creation date, label, last usage, and other metadata relevant to the application password.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential for Infomaniak API access.
- The node makes HTTP requests to the Infomaniak API endpoints.
- Proper configuration of the Infomaniak API credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API token credential will cause authentication failures.
- Providing a non-existent or incorrect Password ID will result in an error.
- Network connectivity issues can prevent successful API calls.
Error messages:
"Failed to retrieve application password <ID>": Indicates the API call did not succeed for the given Password ID. Verify the ID is correct and the API token has sufficient permissions.- Node operation errors may also occur if the API returns an error response or if the request fails due to network or server issues.
Resolution tips:
- Double-check the Password ID input.
- Ensure the API token credential is valid and has required scopes.
- Test connectivity to the Infomaniak API endpoint outside n8n if needed.
Links and References
- Infomaniak API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request node for understanding underlying HTTP calls
- Infomaniak user profile and application password management guides (if publicly available)