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 their related data. Specifically, for the "Profile" resource and the "Delete Profile Phone" operation, it allows users to delete a phone number associated with their profile by specifying the unique identifier of that phone number.
Common scenarios where this node is beneficial include:
- Automating the management of user contact information in Infomaniak profiles.
- Removing outdated or incorrect phone numbers from a user's profile as part of a workflow.
- Integrating profile phone management into larger automation processes involving user data updates.
Example: A workflow that cleans up user profiles by deleting phone numbers that are no longer valid or needed.
Properties
| Name | Meaning |
|---|---|
| Phone ID | The unique identifier (number) of the phone number to be deleted from the user profile. |
Output
The output JSON contains a success confirmation when a phone number is successfully deleted. It has the following structure:
{
"success": true,
"message": "Phone {phoneId} deleted successfully"
}
Where {phoneId} is the ID of the deleted phone number.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential for Infomaniak API access.
- The node makes HTTP DELETE requests to the Infomaniak API endpoint for profile phones.
- No additional external dependencies beyond the Infomaniak API and n8n's HTTP request helper.
Troubleshooting
Common issues:
- Invalid or missing Phone ID parameter will cause failure.
- Authentication errors if the API token is invalid or expired.
- Network connectivity issues preventing API calls.
- Attempting to delete a phone ID that does not exist or is not associated with the authenticated profile.
Error messages:
"Failed to delete phone {phoneId}": Indicates the deletion request was unsuccessful. Verify the phone ID exists and the API token has sufficient permissions.- HTTP 401 Unauthorized or 403 Forbidden errors: Check API credentials.
- NodeOperationError with message
"Failed to delete phone {phoneId}"means the API responded with failure; check logs or API response details.
Resolution tips:
- Ensure the Phone ID is correct and belongs to the current user profile.
- Confirm the API token credential is valid and has required scopes.
- Retry after network issues are resolved.
- Use the "Get Profile Phones" operation to list available phone IDs before attempting deletion.