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 data and related sub-resources. Specifically, for the Profile resource and the Get Profile Email operation, it retrieves a specific email address associated with the current user's profile based on the email type and unique email ID.
Typical use cases include:
- Fetching a particular email address from a user's profile for verification or display.
- Integrating with other systems that require access to specific user email details stored in Infomaniak.
- Automating workflows that depend on retrieving user contact information precisely by type and ID.
Example: You want to retrieve the primary email or an email request entry of a user profile by specifying the email type (email or email_request) and the unique identifier of that email record.
Properties
| Name | Meaning |
|---|---|
| Email Type | The category of the email to retrieve. Options: Email, Email Request. |
| Email ID | The unique numeric identifier of the email record to fetch from the profile's emails. |
Output
The output is a JSON object representing the requested email record from the user's profile. It contains all relevant fields returned by the Infomaniak API for that email entry, such as the email address, status, and metadata.
If the operation succeeds, the node outputs an array with one item containing the email data. If it fails, an error is thrown unless "Continue On Fail" is enabled, in which case the error message is included in the output JSON.
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 endpoint:
https://api.infomaniak.com/2/profile/emails/{emailType}/{emailId} - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Providing an incorrect or non-existent email ID or email type will result in a "Failed to retrieve email" error.
- Network connectivity problems can cause HTTP request failures.
Error messages:
"Failed to retrieve email {emailType}/{emailId}": Indicates the specified email record could not be found or accessed. Verify the email type and ID are correct.- HTTP errors or unexpected API responses will throw a generic failure error.
- If the API returns an error response, it will be surfaced as a node operation error.
Resolution tips:
- Double-check the email type value matches one of the allowed options.
- Confirm the email ID exists in the user's profile via the Infomaniak dashboard or API.
- Ensure the API token has sufficient permissions to read profile emails.
- Enable "Continue On Fail" to handle errors gracefully within workflows.
Links and References
- Infomaniak API Documentation (general reference)
- Infomaniak Profile Emails API endpoint:
/2/profile/emails/{emailType}/{emailId}
This summary focuses exclusively on the Profile resource and the Get Profile Email operation as requested.