WibiClickInstall

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, tasks, suppliers, and settings. Specifically for the User resource and the Get User Profile operation, the node fetches the profile information of the authenticated user associated with a specified website.

Typical use cases include:

• Retrieving the current user's profile details in workflows that require user-specific data.
• Automating user profile synchronization or updates based on external triggers.
• Integrating user profile data into broader business processes like CRM updates or personalized notifications.

Example: You can use this node to get the profile of the logged-in user for a particular website by providing the Website ID, then use the returned profile data downstream in your workflow.

Properties

Output

The output JSON contains the user profile data retrieved from the WibiClick API for the authenticated user linked to the given Website ID. The structure depends on the API response but typically includes fields such as user name, email, address, company info, and other profile-related attributes.

No binary data output is involved in this operation.

Example output snippet (conceptual):

{
  "id": "user-id",
  "firstName": "John",
  "lastName": "Doe",
  "email": "john.doe@example.com",
  "companyEmail": "contact@company.com",
  "address": "123 Main St",
  "city": "Anytown",
  "country": "CountryName",
  "zip": "12345",
  "state": "StateName",
  "marketing": true,
  "updates": false
}

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.
• The Website ID must be valid and correspond to an existing website in the WibiClick system.

Troubleshooting

• Invalid or missing Website ID: Ensure the Website ID provided is correct and exists in the WibiClick system; otherwise, the API may return errors or empty responses.
• Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
• API connectivity issues: Network problems or incorrect API URLs can cause request failures.
• Unexpected API responses: If the API returns unexpected data or errors, check the API documentation or contact WibiClick support.
• Error handling: If the node encounters an error and "Continue On Fail" is not enabled, it will throw an error stopping the workflow. Enable "Continue On Fail" to handle errors gracefully.

Common error message example:

• "Failed to retrieve user profile" — Check API key validity and Website ID correctness.
• HTTP 401 Unauthorized — Invalid or expired API key.
• HTTP 404 Not Found — Website or user profile does not exist.

Links and References

• WibiClick API Documentation (Assumed URL, replace with actual if available)
• n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
• General n8n Credential Setup Guide: https://docs.n8n.io/credentials/overview/

This summary focuses on the User resource and the Get User Profile operation as requested, based solely on static analysis of the provided source code and property definitions.