Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The node provides an interface to update the authenticated user's profile information in a messaging gateway platform. Specifically, the "Update-profile" operation under the "Auth" resource allows users to modify their profile details such as their full name.
This node is beneficial in scenarios where user profile management is required within automated workflows, for example:
- Automatically updating user display names after registration or verification.
- Synchronizing user profile changes from external systems into the messaging platform.
- Allowing users to update their personal information via automated processes.
Properties
| Name | Meaning |
|---|---|
| Full name | The new full name of the user to update in their profile. This is an optional string field. |
Output
The output of this node will be the JSON response returned by the API after updating the user's profile. Typically, this would include the updated profile information or a confirmation of success.
The json output field contains the updated user profile data as returned by the platform's API.
There is no indication that this node outputs binary data.
Dependencies
- Requires an API key credential for authentication with the messaging gateway platform.
- The node makes HTTP PATCH requests to the endpoint
/api/v1/auth/profile. - The base URL and authentication headers are configured using the provided credentials.
Troubleshooting
Common issues:
- Missing or invalid API authentication token can cause authorization errors.
- Providing invalid or malformed input (e.g., non-string for the full name) may result in request validation errors.
- Network connectivity issues could prevent successful API calls.
Error messages:
- Authorization errors typically indicate missing or incorrect API credentials.
- Validation errors will specify which input fields are incorrect or missing.
- Server errors might indicate temporary issues on the platform side; retrying later is recommended.
To resolve these issues:
- Ensure valid API credentials are configured in n8n.
- Validate input data types before execution.
- Check network connectivity and API endpoint availability.
Links and References
- Refer to the messaging gateway platform's API documentation for detailed information on the
/auth/profilePATCH endpoint. - Consult n8n documentation on how to configure API credentials and use HTTP request nodes if needed.