WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node integrates with the WibiClick API to manage various business resources, including employees, jobs, contacts, invoices, and more. Specifically, for the Employee resource with the Add Fuel Expense operation, it allows users to record a fuel expense entry associated with an employee. This is useful for businesses that need to track fuel costs related to employee activities, such as travel or vehicle usage.

Typical use cases include:

  • Logging fuel expenses for employees to monitor and reimburse costs.
  • Integrating fuel expense data into broader financial or payroll workflows.
  • Automating expense tracking in operational processes.

Example: Automatically add a fuel expense record when an employee refuels a company vehicle, capturing details like amount, date, liters, mileage, and description.

Properties

Name Meaning
Website ID The unique identifier of the website under which the employee and expenses are managed.
Fuel Expense Data A collection of fields describing the fuel expense:
- Amount The monetary amount of the fuel expense.
- Date The date when the fuel expense occurred.
- Description A textual description or note about the fuel expense.
- Employee ID The unique identifier of the employee to whom this fuel expense belongs.
- Liters The volume of fuel consumed, measured in liters.
- Mileage The mileage reading associated with the fuel expense (e.g., odometer reading).

Output

The node outputs JSON data representing the response from the WibiClick API after adding the fuel expense. This typically includes confirmation of the created fuel expense record with its details.

The output structure is:

{
  "json": {
    // Response object from the API confirming the added fuel expense
  }
}

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 API key: Ensure the API key credential is correctly set up and valid.
  • Invalid or missing required parameters: For example, websiteId and fuelExpenseData must be provided; missing these will cause errors.
  • API request failures: Network issues or incorrect endpoint URLs can cause failures; verify connectivity and API URL correctness.
  • Incorrect date format: The date field should be a valid datetime string; invalid formats may cause errors.
  • Employee ID not found: If the specified employee does not exist, the API may return an error.

If the node throws errors, check the error message for clues and verify all required inputs are correctly provided.

Links and References

Discussion