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 such as users, notes, jobs, contacts, employees, estimates, invoices, line items, websites, WhatsApp messages, suppliers, settings, technicians, and tasks.
Specifically for the User resource with the Verify Email operation, the node sends a request to verify if a given email address is valid or registered before resetting a user's password. This can be useful in workflows where you want to confirm the existence or validity of a user's email prior to triggering password reset flows or other user-related actions.
Common scenarios:
- Validating user emails during account recovery processes.
- Pre-checking email addresses before sending password reset links.
- Integrating email verification into user management automation.
Example:
You have a workflow that triggers when a user requests a password reset. Before sending the reset link, this node verifies the email to ensure it exists in the system, preventing unnecessary reset attempts.
Properties
| Name | Meaning |
|---|---|
| The email address of the user to verify. This is required for the Verify Email operation. |
Output
The output JSON contains the response from the WibiClick API regarding the email verification status. It typically includes fields indicating whether the email is valid or recognized by the system.
Example output structure:
{
"verified": true,
"email": "name@email.com",
"message": "Email verified successfully"
}
The exact fields depend on the API response but generally confirm the verification result.
Dependencies
- Requires an active connection to the WibiClick API.
- Needs an API key credential configured in n8n for authentication.
- The node uses HTTP requests to communicate with the WibiClick API endpoints.
Troubleshooting
- Invalid or missing API key: Ensure the API key credential is correctly set up in n8n; otherwise, authentication will fail.
- Network issues: If the node cannot reach the WibiClick API, check your network connectivity and firewall settings.
- Invalid email format: The API may reject improperly formatted emails; validate the email format before running the node.
- API errors: If the API returns an error, the node throws an error with the message from the API. Review the error details to resolve issues like rate limits or invalid parameters.
Links and References
- WibiClick API Documentation (Assumed URL for reference)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/