WibiClick icon

WibiClick

Interact with WibiClick API

Actions92

Overview

The node interacts with the WibiClick API to manage various resources such as jobs, notes, contacts, employees, estimates, invoices, line items, websites, WhatsApp messages, users, technicians, tasks, suppliers, and settings. Specifically for the Job resource and the Get Expenses operation, this node retrieves all expenses associated with a specified job.

This operation is useful in scenarios where you want to track or analyze the costs incurred on a particular job, such as for accounting, budgeting, or reporting purposes. For example, a service company could use this to fetch all expenses related to a repair job to calculate profitability or reimbursements.

Properties

Name Meaning
Job ID The unique identifier of the job for which to retrieve expenses. This is a required field.

Output

The output JSON contains the expenses data retrieved from the WibiClick API for the specified job. The structure depends on the API response but generally includes details about each expense item related to the job, such as amount, description, type, date, etc.

Example output structure (simplified):

{
  "expenses": [
    {
      "id": "expense1",
      "amount": 100,
      "description": "Material cost",
      "type": "Materials",
      "date": "2024-06-01"
    },
    {
      "id": "expense2",
      "amount": 50,
      "description": "Travel cost",
      "type": "Travel",
      "date": "2024-06-02"
    }
  ]
}

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the WibiClick API.
  • Requires 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 Job ID: The operation requires a valid Job ID. If missing or incorrect, the API will likely return an error or empty result.
  • API Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Network issues: Connectivity problems can cause request failures.
  • Unexpected API responses: If the API changes or returns unexpected data, the node might fail or produce incorrect outputs.
  • Error handling: If the node is set to continue on failure, it will output an error message in the JSON; otherwise, it will throw an error stopping execution.

Links and References

Discussion