WibiClick

Interact with WibiClick API

Actions92

Overview

This node interacts with the WibiClick API to manage various resources, including employees and their related data. Specifically, for the Employee resource and the Get Employee Fuel Expenses operation, the node retrieves fuel expense records for a specified employee within a given date range.

This operation is useful in scenarios where businesses need to track and analyze fuel expenses incurred by employees, such as for reimbursement, budgeting, or auditing purposes. For example, a company fleet manager can use this node to automatically fetch monthly fuel expenses of drivers to streamline expense reporting.

Properties

Name	Meaning
Employee ID	The unique identifier of the employee whose fuel expenses are to be retrieved.
Start Date	The start date of the period for which to retrieve fuel expenses (inclusive).
End Date	The end date of the period for which to retrieve fuel expenses (inclusive).

These properties must be provided to specify the employee and the time frame for the fuel expense query.

Output

The output JSON contains the fuel expense data returned by the WibiClick API for the specified employee and date range. This typically includes an array or list of individual fuel expense records, each detailing amounts, dates, descriptions, liters, mileage, or other relevant fields as provided by the API.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "fuelExpenses": [
    {
      "date": "2024-05-01",
      "amount": 50.75,
      "liters": 40,
      "mileage": 300,
      "description": "Fuel purchase at Station A"
    },
    {
      "date": "2024-05-15",
      "amount": 60.00,
      "liters": 45,
      "mileage": 350,
      "description": "Fuel purchase at Station B"
    }
  ]
}

Dependencies

Requires an active connection to the WibiClick API.
Requires an API key credential configured in n8n for authentication with the WibiClick service.
The node uses HTTP requests to communicate with the API endpoints.

Troubleshooting

Invalid or missing credentials: Ensure that the API key credential is correctly set up and valid.
Invalid date formats: The start and end dates must be valid ISO 8601 date strings. Invalid dates will cause errors.
Start date after end date: The node checks that the start date is before the end date; otherwise, it throws an error.
Employee ID not found: If the specified employee ID does not exist, the API may return an error or empty results.
API request failures: Network issues or API downtime can cause request failures. Check connectivity and API status.
Error messages from API: The node surfaces error messages from the API response. Review these messages for specific issues.

Links and References

WibiClick API Documentation (Assumed URL, replace with actual if available)
n8n Documentation on Creating Custom Nodes
General info on Handling API Credentials in n8n

This summary focuses on the Employee resource and the Get Employee Fuel Expenses operation as requested, based on static analysis of the provided source code and property definitions.

WibiClickInstall