Actions92
- Contact Actions
- Employee Actions
- Estimate Actions
- Invoice Actions
- Job Actions
- Line Item Actions
- Note Actions
- Setting Actions
- Supplier Actions
- Task Actions
- Technician Actions
- User Actions
- Website Actions
- WhatsApp Actions
Overview
This node integrates with the WibiClick API to perform various operations on multiple resources, including users, notes, jobs, contacts, employees, estimates, invoices, line items, websites, WhatsApp messages, suppliers, settings, technicians, and tasks.
Specifically for the User resource and the Reset Password operation, the node allows resetting a user's password using a provided reset token. This is useful in scenarios where a user has forgotten their password and needs to set a new one securely via a token-based reset process.
Practical example:
You can use this node to automate password resets in your workflow by accepting a reset token (usually sent via email) and a new password, then calling the API to update the user's password without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Password | The new password to set for the user. |
| Reset Token | The password reset token that authorizes the password change. |
These properties are required inputs when performing the "Reset Password" operation on the User resource.
Output
The output JSON object for the "Reset Password" operation includes:
success: A boolean indicating whether the password reset was successful.message: A confirmation message, e.g., "Password reset successfully".email: The email address of the user whose password was reset.
Example output JSON:
{
"success": true,
"message": "Password reset successfully",
"email": "user@example.com"
}
If the reset fails, the node throws an error with details from the API response.
Dependencies
- Requires an active connection to the WibiClick API.
- Requires an API key credential for authentication with the WibiClick API.
- The node uses HTTP requests to communicate with the API endpoints.
- No additional external dependencies beyond the configured API credentials.
Troubleshooting
Common Issues
- Invalid or expired reset token: The API may reject the request if the reset token is invalid or expired. Ensure the token is correct and still valid.
- Missing required parameters: Both the new password and reset token must be provided; otherwise, the request will fail.
- API authentication errors: If the API key is missing, invalid, or revoked, the node will fail to authenticate.
Error Messages
"Unexpected response from server": Indicates the API did not return the expected success confirmation. Verify the token and password correctness.- Errors returned from the API are propagated and include messages from the API response body when available.
- Network or connectivity issues will cause HTTP request failures.
Resolution Tips
- Double-check the reset token and ensure it matches the one issued by the system.
- Confirm the new password meets any complexity requirements enforced by the API.
- Verify that the API key credential is correctly configured and has necessary permissions.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- WibiClick API Documentation (Assumed URL, replace with actual if known)
- General n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- Best practices for password reset flows: https://owasp.org/www-community/controls/Password_Reset
Note: This summary is based solely on static analysis of the provided source code and input property definitions. Runtime behavior depends on the actual API responses and environment configuration.