WibiClickInstall

Overview

This node integrates with the WibiClick API to manage various resources such as employees, jobs, contacts, invoices, and more. Specifically for the Employee resource and the Get Employee Total Fuel Expense operation, it retrieves the total fuel expenses incurred by a specific employee within a defined date range.

This functionality is useful in scenarios where businesses need to track and analyze fuel costs associated with their employees, for example, for reimbursement, budgeting, or auditing purposes.

Practical example:
A company wants to calculate how much fuel expense an employee has accumulated over the last quarter. By providing the employee's ID and the start and end dates of the quarter, this node fetches the total fuel expense from the WibiClick system.

Properties

Output

The output JSON contains the total fuel expense data for the specified employee and date range. The structure corresponds directly to the response from the WibiClick API endpoint /employee-total-fuel-expense/{employeeId}?start={startDate}&end={endDate}.

Typical output fields may include:

• Total amount spent on fuel.
• Possibly additional metadata related to the fuel expenses aggregated over the period.

No binary data output is involved in this operation.

Example output (simplified):

{
  "totalFuelExpense": 123.45,
  "currency": "USD",
  "employeeId": "abc123",
  "startDate": "2024-01-01T00:00:00Z",
  "endDate": "2024-03-31T23:59:59Z"
}

Dependencies

• Requires an active connection to the WibiClick API.
• An API key credential must be configured in n8n to authenticate requests.
• The node uses HTTP requests to communicate with the WibiClick API endpoints.

Troubleshooting

• Invalid or missing Employee ID: Ensure that the Employee ID provided exists in the WibiClick system; otherwise, the API may return an error or empty result.
• Date format errors: The Start Date and End Date must be valid ISO 8601 date strings. Invalid formats will cause the node to throw an error.
• Start Date after End Date: The node checks that the start date is before the end date; if not, it throws an error indicating the date range is invalid.
• API authentication errors: If the API key is incorrect or missing, the node will fail to authenticate. Verify the API key credential configuration.
• Network or API downtime: Temporary network issues or WibiClick API outages can cause request failures. Retrying later or checking API status is recommended.

Common error messages are wrapped and presented as node errors with descriptive messages to help identify the issue.

Links and References

• WibiClick API Documentation (Assumed URL, replace with actual if available)
• n8n Documentation on HTTP Request Node
• n8n Credential Setup Guide for API Keys

If you need details on other operations or resources, feel free to ask!