Uploading Job CSVs
To upload a job CSV users must select the Upload Jobs option via the Add button.
Job CSV Fields
Field name | Example | Details | Requirement |
Address | 123 Street, Sydney NSW, 2000, Australia | If left blank, NowGo prompts “Please enter a recognisable address to locate”. | Mandatory |
Type | Pickup, Dropoff, Transfer | If left blank NowGo automatically assigns the “Attend” job type. Best Practice - Assign the type to the stop action expected to be taken. | Required |
Time Window Start | 10:00 | Start time for the job. | Required |
Time Window End | 23:00 | End time for the job. Defaults to 5:00pm if not specified. | Required |
Service time | 180 | Time that the job will take in seconds (e.g. 180 for 3 minutes). Defaults to 2 minutes (120) if not specified. | Required |
Date or Start Date | 3/9/21 | Start date of the job. Also used as the end date unless End Date is specified. | Required |
End Date | 4/9/21 | End date of the job. If not specified, Date/Start Date will be used instead | Optional |
Latitude | -33.896273 | Will not be recognized if the corresponding Longitude is not included | Optional |
Longitude | 150.969011 | Will not be recognized if the corresponding Latitude is not included | Optional |
Driver String: Driver Email OR Driver | OR
| String identifier for a driver, using either Driver Email or Driver Ext Ref. If one of these is present in a stop row, this stop will be assigned to that matching driver.
| Optional |
Shift Name |
| If supplied, and: this row also has a matching driver, Then: The resulting shift should have the supplied name | Optional |
Capacity Costs | (weight, 1000) (volume, 100) | The LHS value in the bracket is the Capacity cost of this job. If the shift has a vehicle/vehicle type with capacities, then this job must not exceed capacity limits of the vehicle/vehicle type | Optional |
Requirements | (has-crane, true) (vehicle-height, 100) | The LHS value in the bracket is the | Optional |
Vehicle Preferences | (car, allowed) | The LHS value in the bracket is the
| Optional |
Vehicle Type Preferences | (car, allowed) | The LHS value in the bracket is the
| Optional |
Job Reference | {1, 2, 3, …} | Used to link stops as part of the same job e.g., Job Reference: Pickup = “1”; Deliver = “2” For CSV, rows must be uploaded in sequential order i.e., pickup before delivery | Optional |
Job Number | {1, 2, 3, …} | Used to specify the order of stops within a job. Example - this kind of data will give a job with job ref=potato, and put the first stop ahead of the second stop in the job order.
| Optional |
Customer Communications Plan Comms Plan ID OR Comms Plan | 216
OR
start_consignment_comms | Id OR Ext Ref for communications plan. Requires comms plans to be set up correctly. | Optional |
Contact Email | The customer’s email address. If you want to send emails via Customer Comms - use this | Optional | |
Contact Phone | ‘+6141 111 111’ | The customer’s phone number If you want to send SMS via Customer Comms - use this. It will also allow drivers to call a customer using the in-app button | Optional |
Contact Name | ‘Chris Olsson’ | The customer’s name. This can be referenced via customer comms (i.e. | Optional |
Priority |
| Priority to assign to the created job. | Optional |
Allowed Drivers |
| Sets the list of allowed drivers for a job. Accepts ID, ext ref, and email. Comma separated. | Optional |
Plan Number |
| Determines which plan an upload is placed in (see “Creating multiple plans at once” below). | Optional |
The address field is the only mandatory field when uploading a Job CSV. Doing this will generate a series of defaults for other fields which in practice will produce a result, however it will be very limited in testing or showcasing NowGo functionality.
The recommendation is to populate all the mandatory and required fields.
Creating multiple plans at once
You can create multiple plans at once using the Plan Number column. One plan will be created for each unique value in the column, with stops split between them.
Stop Custom Data
You can add custom data fields to NowGo in the Dashboard.
Click on your email address on the top right
Click on Settings from the drop-down menu
Click on Dashboard Configuration, then click on Stop custom data from the side menu
Click on Add New;
Enter the stop field details and a JSONpath;
Click on Save Changes.
NowGo needs a JSONPath to the custom data you want to show. This path can point to lists as well as single items. For more information on how to use JSONPath, we like Stefan Goessner's guide.
If you added custom data via CSV, the JSONPath will simply be $. followed by the column header. For example, if the column header is booking, the path will be $.booking.
Field name | Example | Details | Requirement |
booking | 20220330-1234-01 | Based on the example given in the dashboard, this would be custom data related to relevant booking details | optional |