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 integrates with the WibiClick API to manage various resources related to business operations. Specifically, for the Employee resource with the Get Employees operation, it retrieves a list of employees associated with a specified website. This is useful in scenarios where you want to automate workflows involving employee data retrieval, such as syncing employee lists with other systems, generating reports, or triggering actions based on employee information.
For example, you might use this node to:
- Fetch all employees from a particular website to update an HR system.
- Retrieve employee data to send notifications or assign tasks automatically.
- Integrate employee information into payroll or attendance systems.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website for which to retrieve employees. |
| Limit | Maximum number of employee records to return. |
| Offset | Number of employee records to skip (used for pagination). |
Output
The output is a JSON object containing the list of employees retrieved from the WibiClick API. The structure typically includes employee details such as names, contact information, roles, and other metadata as provided by the API response.
Example output structure (simplified):
{
"employees": [
{
"id": "employee-id-1",
"firstName": "John",
"lastName": "Doe",
"email": "john.doe@example.com",
"phone": "1234567890",
"location": "Office Location",
"description": "Job description or notes"
},
{
"id": "employee-id-2",
"firstName": "Jane",
"lastName": "Smith",
"email": "jane.smith@example.com",
"phone": "0987654321",
"location": "Office Location",
"description": "Job description or notes"
}
// ...more employees
]
}
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.
- Network access to the WibiClick API endpoint is necessary.
Troubleshooting
- Invalid Website ID: If the website ID is incorrect or does not exist, the API may return an error or empty results. Verify the website ID before running the node.
- API Authentication Errors: Ensure that the API key credential is valid and has sufficient permissions.
- Pagination Issues: If the limit and offset parameters are not set correctly, you might miss some employees or get duplicate data. Adjust these parameters according to your data size.
- Network Errors: Connectivity issues can cause request failures. Check network settings and API availability.
- Unexpected API Response: If the API changes or returns unexpected data, the node might fail. Review the API documentation or contact support if needed.
Links and References
- WibiClick API Documentation (Assumed link; replace with actual if available)
- n8n Documentation on HTTP Request Node for understanding API calls
- General n8n Node Development Guide