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
The node interacts with the WibiClick API to manage various resources, including users. Specifically, for the User resource and the Update User Profile operation, it allows updating the profile information of an authenticated user. This is useful in scenarios where you want to programmatically update user details such as name, email, address, or marketing preferences within your workflows.
Practical examples include:
- Automatically updating a user's profile after they submit a form.
- Syncing user profile changes from another system into WibiClick.
- Managing user preferences like marketing opt-ins based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Profile Data | A collection of user profile fields that can be updated. Options include: |
| - Address: Address of the user | |
| - City: City of the user | |
| - Company Email: Company email of the user | |
| - Country: Country of the user | |
| - Email: Email of the user | |
| - First Name: First name of the user | |
| - Last Name: Last name of the user | |
| - Marketing: Boolean indicating if the user has opted in for marketing | |
| - State: State of the user | |
| - Updates: Boolean indicating if the user has opted in for updates | |
| - ZIP: ZIP code of the user |
These fields are provided as a collection where you can specify one or more fields to update in the user's profile.
Output
The output JSON contains the response from the WibiClick API after attempting to update the user profile. It typically includes the updated profile data or confirmation of the update operation.
Example output structure:
{
"json": {
// The API response object representing the updated user profile
}
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WibiClick API via an API key credential.
- The node expects the API URL and API key to be configured in the credentials.
- No additional environment variables are required beyond the API authentication.
Troubleshooting
- API Authentication Errors: Ensure the API key credential is correctly set up and valid.
- Invalid Profile Data: If the API rejects the update due to invalid or missing fields, verify that the profile data fields conform to expected formats (e.g., valid email format).
- Network Issues: Connectivity problems with the WibiClick API endpoint will cause request failures.
- Partial Updates: Only provide fields you want to update; omitting fields will leave them unchanged.
- Error Handling: If the node encounters an error during execution, it throws an error unless "Continue On Fail" is enabled, in which case it outputs an error message per item.
Links and References
- WibiClick API Documentation (Assumed, replace with actual link if available)
- n8n Documentation on Creating Custom Nodes
- General info on HTTP Request Node used internally for API calls