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 profile information and related sub-resources. Specifically, the "Get Profile" operation retrieves the current user's profile data from Infomaniak. This is useful in scenarios where you want to fetch and use user profile details within an automation workflow, such as personalizing communications, syncing user data with other systems, or auditing user information.
For example, you might use this node to:
- Retrieve the logged-in user's profile details to display or log them.
- Load additional related data about the user by specifying extra options.
- Integrate user profile data into a CRM or database for further processing.
Properties
| Name | Meaning |
|---|---|
| Profile Options | Collection of optional parameters to customize the profile retrieval. Contains: |
| - With | A string to specify additional related resources to load along with the profile data. |
The "With" option allows loading extra related data about the profile, enhancing the returned information beyond basic profile fields.
Output
The node outputs JSON data representing the user's profile information as returned by the Infomaniak API. The structure typically includes standard profile fields such as name, email, locale, timezone, and potentially additional related data if requested via the "With" option.
The output is an array of JSON objects (usually one object per input item), each containing the profile data under the json key.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for Infomaniak API access.
- The node makes HTTP requests to Infomaniak's REST API endpoints.
- Proper configuration of the Infomaniak API credentials in n8n is necessary.
Troubleshooting
- Failed to retrieve profile: This error indicates that the API request did not succeed. Possible causes include invalid or expired API tokens, network issues, or API service downtime. Verify your API credentials and network connectivity.
- Invalid "With" parameter: If the "With" option is used incorrectly or specifies unsupported values, the API may return errors or incomplete data. Ensure the value matches supported resource names as per Infomaniak API documentation.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Infomaniak API Documentation (general reference for available endpoints and parameters)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made internally)