Planka icon

Planka

Interact with Planka API

Overview

The Planka n8n node's "👤 USER" resource with the "🔑 Update User Password" operation allows you to update the password of an existing user in your Planka instance. This is useful for administrative workflows where you need to reset or change a user's password programmatically, such as onboarding, security policy enforcement, or automated account management.

Practical examples:

  • Automatically resetting a user's password after a security incident.
  • Integrating with HR systems to update passwords when employees change roles.
  • Providing self-service password reset flows via n8n automations.

Properties

Name Type Meaning
User ID String The unique identifier of the user whose password will be updated. Required.
Password String The new password to set for the user. Required. (Input is masked for security.)

Output

The node returns the updated user object in the json field. The structure typically includes user details such as:

{
  "id": "string",
  "name": "string",
  "email": "string",
  "username": "string",
  // ...other user fields
}
  • If the operation fails and "Continue On Fail" is enabled, the output will contain an error message:
{
  "error": "Error message text"
}

Dependencies

  • External Service: Requires access to a running Planka API instance.
  • Authentication: Needs valid Planka API credentials configured in n8n under the name plankaApi.

Troubleshooting

Common Issues:

  • Invalid User ID: If the provided User ID does not exist, the API will return an error.
  • Weak Password: If the new password does not meet Planka's password policy, the request may fail.
  • Missing Credentials: If the Planka API credentials are not set up in n8n, the node will not function.

Error Messages:

  • "User not found": Check that the User ID is correct.
  • "Password does not meet requirements": Ensure the password meets the minimum length and complexity required by Planka.
  • "401 Unauthorized": Verify that your API credentials are correct and have sufficient permissions.

Links and References


Discussion