Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Update User" operation in this node allows you to modify the details of an existing user in the Zep Cloud v3 system. This includes updating the user's email, first name, last name, metadata, and optionally providing instructions for fact rating associated with the user.
This operation is useful in scenarios where user information needs to be kept current or enriched with additional data, such as updating contact details, adding organizational metadata, or customizing how facts related to the user are rated for relevance and accuracy.
Practical examples:
- Updating a user's email address after they change it.
- Adding or modifying metadata like department or role to better categorize users.
- Providing custom instructions for fact rating to tailor how information related to the user is evaluated.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to update. This is required to specify which user record to modify. |
The new email address of the user. Example: user@example.com. Optional; if not provided, the email remains unchanged. |
|
| First Name | The new first name of the user. Example: John. Optional; if not provided, the first name remains unchanged. |
| Last Name | The new last name of the user. Example: Doe. Optional; if not provided, the last name remains unchanged. |
| Metadata | A JSON object containing metadata associated with the user. Example: {"department": "engineering", "role": "developer"}. Optional; used to add or update custom user attributes. |
| Fact Rating Instruction | Optional instruction to use for fact rating, consisting of: - Instruction: Main instruction text (e.g., "Rate facts based on relevance and accuracy"). - High Rating Example: Example of a highly rated fact. - Medium Rating Example: Example of a medium-rated fact. - Low Rating Example: Example of a low-rated fact. |
Output
The output is a JSON object representing the updated user data as returned by the Zep Cloud API. It typically includes the user's updated fields such as user ID, email, first name, last name, metadata, and any fact rating instructions set.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Zep Cloud v3 API.
- Requires an API key credential configured in n8n for authentication with the Zep API.
- The base URL for API requests is
https://api.getzep.com. - The node uses HTTP PATCH method to update user data via the endpoint
/api/v2/users/{userId}.
Troubleshooting
Common issues:
- Providing an invalid or non-existent User ID will result in an error indicating the user could not be found.
- Malformed JSON in the Metadata field can cause request failures.
- Omitting required credentials or having expired/invalid API keys will cause authentication errors.
Error messages and resolutions:
"Unknown user operation: update": Ensure the operation parameter is correctly set to "update".- HTTP 401 Unauthorized: Verify that the API key credential is correctly configured and valid.
- HTTP 400 Bad Request: Check that all input fields, especially JSON metadata and fact rating instructions, are properly formatted.
"User not found"or similar: Confirm the User ID exists in the Zep system before attempting to update.
Links and References
- Zep Cloud API Documentation (for detailed API endpoints and payload structures)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)
If you need further details about other operations or resources, feel free to ask!