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 manage various resources such as contacts, jobs, notes, employees, estimates, invoices, line items, websites, WhatsApp messages, users, technicians, tasks, suppliers, and settings. Specifically for the Contact resource with the Get operation, it retrieves detailed information about a specific customer/contact from a given website.
Typical use cases include:
- Fetching customer details by their unique ID within a specified website.
- Integrating customer data retrieval into automated workflows for CRM, support, or marketing purposes.
- Using the contact information to trigger further actions like sending messages, creating jobs, or updating records.
Example: You want to get the full profile of a customer identified by their Customer ID on a particular website to personalize communication or update other systems accordingly.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website where the contact/customer is registered. |
| Customer ID | The unique identifier of the customer/contact whose details you want to retrieve. |
Output
The output is a JSON object containing the customer's data as returned by the WibiClick API. This typically includes all available fields related to the customer such as name, contact details, address, email, phone number, and any other metadata stored in the system.
The structure depends on the API response but generally represents a single customer record with all associated attributes.
No binary data output is involved in this operation.
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
- Missing or invalid Website ID or Customer ID: Ensure both IDs are provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API endpoint errors: If the customer does not exist or the ID is incorrect, the API may return an error or empty response.
- Network issues: Check connectivity to the WibiClick API service.
- Error messages: The node throws errors with messages from the API or generic messages if unexpected responses occur. Review these messages to identify issues.
Links and References
- WibiClick API Documentation (Assumed URL for reference)
- n8n HTTP Request Node documentation for understanding request handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/