Actions3
- Estimate Actions
- Request Actions
- Worth Actions
Overview
This node calculates the profitability or worth of a ride based on various input parameters such as distance, duration, gross fare, platform fee, and costs related to fuel, maintenance, and opportunity cost. It is useful for drivers or ride-sharing service providers to determine if a ride is financially viable before accepting it. For example, a driver can input the expected distance and duration of a ride along with associated costs and fees to get a clear indication of the ride's net worth and decide whether to accept the ride.
Use Case Examples
- A driver wants to calculate if a ride with a 10 km distance and 15 minutes duration, with a gross fare of $20 and a platform fee of 20%, is profitable after accounting for fuel, maintenance, and opportunity costs.
- A ride-sharing service provider uses the node to automate the evaluation of ride requests to filter out those that do not meet a minimum profit threshold.
Properties
| Name | Meaning |
|---|---|
| Distance (km) | The distance of the ride in kilometers. |
| Duration (min) | The duration of the ride in minutes. |
| Pickup Distance (km) | The distance traveled to reach the pickup location in kilometers. |
| Pickup Duration (min) | The time taken to reach the pickup location in minutes. |
| Gross Value (fare) | The total fare amount for the ride before deductions. |
| Platform Fee (%) | The percentage fee taken by the platform from the gross fare. |
| Fuel Cost per km | The cost of fuel per kilometer traveled. |
| Maintenance per km | The maintenance cost per kilometer traveled. |
| Opportunity Cost per min | The cost of lost opportunity per minute spent on the ride. |
| Min Profit Threshold | The minimum profit required to consider the ride worthwhile. |
Output
JSON
netWorth- The calculated net worth or profitability of the ride after all costs and fees.isWorthIt- Boolean indicating if the ride meets the minimum profit threshold and is worth accepting.
Dependencies
- An API key credential for Uber OAuth2 authentication is optionally supported but not required for this operation.
Troubleshooting
- Ensure all required numeric inputs (distance, duration, gross fare) are provided and valid numbers to avoid calculation errors.
- If the platform fee percentage is set outside the 0-100 range, the calculation may be incorrect; ensure it is within this range.
- If the node throws an error related to API requests, check the Uber OAuth2 credentials if used, or verify network connectivity.