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
This node integrates with the WibiClick API to manage various resources related to business operations, including jobs, contacts, employees, invoices, and more. Specifically, for the Job resource with the Add Expense operation, it allows users to add an expense entry to a specific job by providing details such as amount, description, and type of the expense.
Common scenarios where this node is beneficial include:
- Tracking additional costs incurred during a job.
- Automating expense logging in workflows that manage job lifecycle.
- Integrating expense data into broader financial or project management systems.
Practical example:
- After completing a service job, automatically add expenses like materials or travel costs to the job record for accurate billing and reporting.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier of the job to which the expense will be added. |
| Expense Data | A collection of fields describing the expense: |
| Amount | The monetary value of the expense. |
| Description | A textual description explaining the nature of the expense. |
| Type | The category or type of the expense (e.g., materials, travel, labor). |
Output
The output JSON contains the response from the WibiClick API after adding the expense to the specified job. This typically includes confirmation details about the newly added expense or the updated job expense list.
Example output structure:
{
"json": {
// API response object confirming the added 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 Job ID: The operation requires a valid Job ID. Ensure the Job ID provided exists and is correctly formatted.
- API Authentication Errors: If the API key is missing, invalid, or expired, requests will fail. Verify the API key credential configuration.
- Network Issues: Connectivity problems can cause request failures. Check network access to the WibiClick API endpoint.
- Invalid Expense Data: Providing incorrect types or missing required fields in the expense data may result in API errors. Validate input data before execution.
- API Response Errors: The node throws errors if the API response indicates failure. Review error messages returned by the API for specific issues.
Links and References
- WibiClick API Documentation (Assumed URL, replace with actual if available)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/