Actions46
- 🏢 PROJECT Actions
- 📋 BOARD Actions
- 📝 CARD Actions
- ➕ Create Card
- 🔍 Get Card
- ✏️ Update Card
- 🗑️ Delete Card
- 🏷️ Add Label to Card
- 🚫 Remove Label from Card
- 👤 Add Member to Card
- 🚫 Remove Member from Card
- ✅ Create Task in Card
- 🔄 Update Task
- 🗑️ Delete Task
- 📎 Create Attachment in Card
- ✏️ Update Attachment
- 🗑️ Delete Attachment
- 📋 Get All Card Actions
- 💬 Create Comment on Card
- ✏️ Update Comment
- 🗑️ Delete Comment
- 👤 USER Actions
Overview
The Update User Email operation for the 👤 USER resource in this n8n node allows you to change the email address of an existing user in a Planka instance. This is useful for administrative tasks such as correcting typos, updating contact information when a user changes their email provider, or managing user accounts centrally.
Practical scenarios:
- An employee updates their corporate email address and needs it reflected in Planka.
- A user requests a correction to their registered email due to a typo.
- Automated workflows that synchronize user data between HR systems and Planka.
Properties
| Name | Type | Meaning |
|---|---|---|
| User ID | String | The unique identifier of the user whose email will be updated. Required. |
| String | The new email address to assign to the user. Required. |
Output
The output will be a JSON object representing the updated user record as returned by the Planka API after the email update. The structure typically includes user details such as id, name, email, username, and other profile fields.
Example output:
{
"id": "123",
"name": "Jane Doe",
"email": "new.email@example.com",
"username": "janedoe",
// ...other user fields
}
If an error occurs and "Continue On Fail" is enabled, the output will include an error message:
{
"error": "User not found"
}
Dependencies
- Planka API: Requires access to a running Planka instance with API enabled.
- API Credentials: You must configure valid Planka API credentials in n8n under the credential type
plankaApi.
Troubleshooting
Common issues:
- Invalid User ID: If the provided User ID does not exist, the API will return an error (e.g., "User not found").
- Email Already In Use: Attempting to set an email that is already assigned to another user may result in a conflict error.
- Missing Permissions: The API credentials used must have permission to update users.
- Malformed Email: Providing an invalid email format may cause validation errors.
Error messages and resolutions:
"User not found": Check that the User ID is correct and exists in Planka."Email already taken": Use a different email address that is not already registered."Unauthorized": Ensure your API credentials are correct and have sufficient permissions.
