Actions5
Overview
The "Mileage Allowance" resource with the "Create" operation in this node allows users to record mileage allowance entries for a company. This is useful for expense tracking related to business travel by car, where users can log the date, distance traveled, and optionally associate the entry with a specific vehicle and add a memo.
Common scenarios include:
- Employees submitting mileage claims for reimbursement.
- Accounting teams tracking travel expenses per company car.
- Automating mileage expense reports based on logged trips.
Example: A user logs a 28 km trip made on a certain date using a company car, adding a note about the purpose of the trip.
Properties
| Name | Meaning |
|---|---|
| Company | The company associated with the mileage allowance entry. Can be selected from a list or entered as an ID. |
| Date | The date when the mileage was recorded (date and time). |
| Memo | An optional text note or description related to the mileage entry. |
| Distance | The distance traveled in kilometers (numeric value). |
| Car ID | The identifier of the car used for the trip. Can be selected from a list or entered as an ID. |
Output
The node outputs JSON data representing the created mileage allowance record. This typically includes details such as the mileage ID, associated company, date, distance, memo, and car information.
No binary data output is indicated.
Dependencies
- Requires an API authentication token credential to connect to the external Dougs service.
- The node communicates with the Dougs API at
https://app.dougs.fr. - The node depends on internal methods to fetch lists of companies and cars for resource locator properties.
Troubleshooting
- Missing Handler Error: If the node throws an error like
Handler missing for resource "mileage-allowance" and operation "create"., it indicates that the implementation for this resource-operation pair is not found. Ensure the node version supports this operation. - Invalid Company or Car ID: Providing an incorrect or non-existent company or car ID may cause API errors. Use the provided list mode to select valid IDs.
- Distance Not Provided or Invalid: The distance must be a numeric value; omitting or entering invalid data may cause failures.
- API Authentication Issues: Ensure the API key or authentication token is correctly configured and has sufficient permissions.
Links and References
- Dougs API Documentation (general reference for the API endpoint)
- n8n documentation on Resource Locator Parameter for understanding how company and car selections work.