assign_driver
ChatGPTAssign a driver to a route (replacing any driver already on it). Give the driver by name or uuid; a name is matched against the organization's drivers. Route uuids come from show_on_map or list_routes. Only planned or published routes can take a driver; on a published route the driver sees it in their Routific app straight away, so confirm with the user first if the route is published. Only call this after the user has explicitly confirmed — it can't be undone. Docs: https://api-docs.routific.com/reference/assign-driver.
create_optimization
ChatGPTOnly for when the user chose the plan in chat. If the user hasn't said whether they want the plan here in chat or set up on a map in their Routific account, ask them first and wait for the answer — don't call any planning tool until they've chosen. Run a full multi-vehicle route optimization on YOUR Routific organization (requires signing in). This is a self-contained 'one-off' schedule: pass the fleet inline as routesData (vehicles, up to 500) and the stops inline as ordersData (deliveries/visits, up to 5,000) — no workspace or pre-created records are needed. The engine assigns every order to a route while respecting time windows, capacity, and tags. Waits for the result (up to ~45s) and returns the solved plan: each vehicle's stops in order with ETAs, plus anything left unscheduled. Very large runs may still be going when it returns; then it gives an actionUuid to check with get_optimization and fetch with get_schedule_solution. Nothing is saved to the user's workspace. Docs: https://api-docs.routific.com/reference/one-off-scheduling.
create_orders
ChatGPTCreate orders (visits) in a workspace (batch). Each order: { locations (required): [{ address, latitude?, longitude? }], name?, email?, duration? (service time in SECONDS, e.g. 300 for 5 minutes), phone?, instructions?, load?, timeWindows?, packages?, tags?, customFields?, deliveryDate? }. Set deliveryDate (YYYY-MM-DD) so the orders can be scheduled for that day with schedule_orders. Orders count toward the account's monthly plan.
create_routes
ChatGPTCreate routes in a workspace (batch, max 50). Each route: { name, date (ISO8601), startTime, endTime (military time), startLocation?, endLocation?, capacity?, tags? }. One route per driver or vehicle. startLocation/endLocation: pass { address } (full street address with city and region — it's looked up on the map for you) or { latitude, longitude }. Never invent coordinates. The result lists where each address was placed under geocoded_depots; tell the user, so a wrong match is caught. Omit the locations if the user hasn't given a depot.
delete_order
ChatGPTPermanently delete a single order by uuid, including one already on a route (the route is re-timed). Deleting a scheduled order is async (poll with get_order_action). Only call this after the user has explicitly confirmed — it can't be undone.
delete_orders
ChatGPTPermanently delete multiple orders in a workspace by uuid (max 500), including ones already on a route. May be async (poll with get_order_action). Only call this after the user has explicitly confirmed — it can't be undone.
get_optimization
ChatGPTPoll the status/result of an optimization started with create_optimization, by its actionUuid. Returns { status } while the job is pending, and the solved schedule once the status is finished (or an error once failed). Docs: https://api-docs.routific.com/reference/fetch-schedule-status.
get_order
ChatGPTGet a single order (visit) by its uuid.
get_order_action
ChatGPTPoll an order async action (update/delete) by its actionUuid.
get_route
ChatGPTGet a single route by its uuid.
get_route_action
ChatGPTCheck on a publish that was still running when publish_routes returned, by its actionUuid. Returns each route's outcome. Docs: https://api-docs.routific.com/reference/fetch-route-publishing-status.
get_route_timeline
ChatGPTGet a route's timeline (stops in order with ETAs), keyset-paginated.
get_schedule_action
ChatGPTPoll a schedule action's status by its actionUuid.
get_schedule_solution
ChatGPTFetch the full solved solution of a finished optimization, by its actionUuid: { routes, orders, unscheduledOrders } — the per-vehicle stop sequences with ETAs, plus any orders that could not be scheduled. Call this once get_optimization reports the action finished (use the same actionUuid returned by create_optimization). Docs: https://api-docs.routific.com/reference/fetch-scheduled-solution.
list_drivers
ChatGPTList the drivers in the user's Routific organization (name and uuid). Use it to show who can be assigned to a route; assign_driver also accepts a driver's name directly. Docs: https://api-docs.routific.com/reference/fetch-drivers.
list_routes
ChatGPTList a workspace's routes for a date: uuid, name, driver, status, order count, working time, distance. Set include_orders to also get each route's order uuids in stop order — the way to find a day's orders for follow-up edits (update_order / update_orders / delete_orders). Docs: https://api-docs.routific.com/reference/fetch-routes.
list_schedules
ChatGPTList schedules (keyset-paginated). Filter by workspace, date, or status.
list_workspaces
ChatGPTList the organization's workspaces (keyset-paginated). Workspaces scope routes/orders.
optimize_route
ChatGPTOnly for when the user chose the plan in chat. If the user hasn't said whether they want the plan here in chat or set up on a map in their Routific account, ask them first and wait for the answer — don't call any planning tool until they've chosen. Optimize the visiting order of a list of addresses (a single-vehicle delivery/service route). Returns the optimal stop sequence with an ETA and driving distance for each stop, plus total travel time and distance. Addresses are geocoded automatically; include city and region in every address for reliable results. Maximum 8 stops per request (free demo limit). Never split a longer stop list into multiple calls: chunks optimized separately are not jointly optimal, so the combined result would NOT be an optimized route. If there are more than 8 stops or several drivers, use create_optimization instead (requires signing in). Docs: https://docs.routific.com/reference/vrp-long.
publish_routes
ChatGPTPublish a day's routes to the drivers: they appear in the drivers' Routific mobile app and customer notifications start. It publishes EVERY route in the workspace on that date (routes without stops, and published routes that haven't changed, are skipped; changed ones are re-sent and marked Updated in the app). Give each route a driver first (assign_driver). Before calling, tell the user which routes and drivers will go out (list_routes) and only call after they've explicitly confirmed — it notifies drivers and customers. Unpublishing is done in the Routific app. Waits for the result and returns each route's outcome. Docs: https://api-docs.routific.com/reference/publish-routes.
schedule_orders
ChatGPTRun Routific's optimizer on the user's workspace for a date: assigns the orders to the routes and sequences each route, like the Schedule button in the app. With only a date, it schedules every unscheduled order for that date across all unlocked routes; pass orders/routes to restrict it. The result is saved in the workspace. When setting up a plan from chat, pass only the orders and routes you just created. Waits for the run to finish (up to ~45s) and returns how many orders were scheduled; then share view_in_app as an 'Open in Routific' link. If it's still running when it returns, check again with get_schedule_action. Docs: https://api-docs.routific.com/reference/schedule-orders.
show_on_map
ChatGPTOnly for when the user chose the map in Routific (or asked for Routific, a map, or dispatch). If the user hasn't said whether they want the plan here in chat or set up on a map in their Routific account, ask them first and wait for the answer — don't call any planning tool until they've chosen. Put a plan on the map in the user's Routific account in ONE call: adds the stops as orders for the date, creates a route per driver (depot addresses are looked up on the map), optimizes only those orders onto those routes, waits for the result, and returns the 'Open in Routific' link (view_in_app) with a short summary — no stop list, since the user sees the plan in Routific. Use this when the user wants the result on a map / in Routific — instead of, not after, optimizing in chat. Nothing else in their workspace is touched. Orders count toward their plan. Answer as the result's reply field says: link first.
unassign_driver
ChatGPTRemove the driver from a route, leaving it without one. Only planned or published routes; on a published route the driver loses it from their Routific app. Only call this after the user has explicitly confirmed — it can't be undone. Docs: https://api-docs.routific.com/reference/unassign-driver.
update_order
ChatGPTChange fields on an existing order (scheduled or not). Pass ONLY the fields to change — everything else is kept; null clears a field. Pass locations to change the address (it re-geocodes); duration is service time in SECONDS (300 = 5 minutes). Editing a scheduled order re-times its route and may be async (returns an action to poll with get_order_action).
update_orders
ChatGPTApply the same change to many orders in one call (up to 200) — use this instead of calling update_order once per order. Pass the order uuids (from show_on_map or list_routes with include_orders), the fields to change in order (everything else is kept; duration is in SECONDS), and/or addTags / removeTags to change tags while keeping the existing ones. Note: tags are routing requirements — an order tagged X can only go on a route tagged X — so for a plain label prefer customFields or instructions. Returns per-order results.
assign_driver
ClaudeAssign a driver to a route (replacing any driver already on it). Give the driver by name or uuid; a name is matched against the organization's drivers. Route uuids come from show_on_map or list_routes. Only planned or published routes can take a driver; on a published route the driver sees it in their Routific app straight away, so confirm with the user first if the route is published. Only call this after the user has explicitly confirmed — it can't be undone. Docs: https://api-docs.routific.com/reference/assign-driver.
create_optimization
ClaudeOnly for when the user chose the plan in chat. If the user hasn't said whether they want the plan here in chat or set up on a map in their Routific account, ask them first and wait for the answer — don't call any planning tool until they've chosen. Run a full multi-vehicle route optimization on YOUR Routific organization (requires signing in). This is a self-contained 'one-off' schedule: pass the fleet inline as routesData (vehicles, up to 500) and the stops inline as ordersData (deliveries/visits, up to 5,000) — no workspace or pre-created records are needed. The engine assigns every order to a route while respecting time windows, capacity, and tags. Waits for the result (up to ~45s) and returns the solved plan: each vehicle's stops in order with ETAs, plus anything left unscheduled. Very large runs may still be going when it returns; then it gives an actionUuid to check with get_optimization and fetch with get_schedule_solution. Nothing is saved to the user's workspace. Docs: https://api-docs.routific.com/reference/one-off-scheduling.
create_orders
ClaudeCreate orders (visits) in a workspace (batch). Each order: { locations (required): [{ address, latitude?, longitude? }], name?, email?, duration? (service time in SECONDS, e.g. 300 for 5 minutes), phone?, instructions?, load?, timeWindows?, packages?, tags?, customFields?, deliveryDate? }. Set deliveryDate (YYYY-MM-DD) so the orders can be scheduled for that day with schedule_orders. Orders count toward the account's monthly plan.
create_routes
ClaudeCreate routes in a workspace (batch, max 50). Each route: { name, date (ISO8601), startTime, endTime (military time), startLocation?, endLocation?, capacity?, tags? }. One route per driver or vehicle. startLocation/endLocation: pass { address } (full street address with city and region — it's looked up on the map for you) or { latitude, longitude }. Never invent coordinates. The result lists where each address was placed under geocoded_depots; tell the user, so a wrong match is caught. Omit the locations if the user hasn't given a depot.
delete_order
ClaudePermanently delete a single order by uuid, including one already on a route (the route is re-timed). Deleting a scheduled order is async (poll with get_order_action). Only call this after the user has explicitly confirmed — it can't be undone.
delete_orders
ClaudePermanently delete multiple orders in a workspace by uuid (max 500), including ones already on a route. May be async (poll with get_order_action). Only call this after the user has explicitly confirmed — it can't be undone.
get_optimization
ClaudePoll the status/result of an optimization started with create_optimization, by its actionUuid. Returns { status } while the job is pending, and the solved schedule once the status is finished (or an error once failed). Docs: https://api-docs.routific.com/reference/fetch-schedule-status.
get_order
ClaudeGet a single order (visit) by its uuid.
get_order_action
ClaudePoll an order async action (update/delete) by its actionUuid.
get_route
ClaudeGet a single route by its uuid.
get_route_action
ClaudeCheck on a publish that was still running when publish_routes returned, by its actionUuid. Returns each route's outcome. Docs: https://api-docs.routific.com/reference/fetch-route-publishing-status.
get_route_timeline
ClaudeGet a route's timeline (stops in order with ETAs), keyset-paginated.
get_schedule_action
ClaudePoll a schedule action's status by its actionUuid.
get_schedule_solution
ClaudeFetch the full solved solution of a finished optimization, by its actionUuid: { routes, orders, unscheduledOrders } — the per-vehicle stop sequences with ETAs, plus any orders that could not be scheduled. Call this once get_optimization reports the action finished (use the same actionUuid returned by create_optimization). Docs: https://api-docs.routific.com/reference/fetch-scheduled-solution.
list_drivers
ClaudeList the drivers in the user's Routific organization (name and uuid). Use it to show who can be assigned to a route; assign_driver also accepts a driver's name directly. Docs: https://api-docs.routific.com/reference/fetch-drivers.
list_routes
ClaudeList a workspace's routes for a date: uuid, name, driver, status, order count, working time, distance. Set include_orders to also get each route's order uuids in stop order — the way to find a day's orders for follow-up edits (update_order / update_orders / delete_orders). Docs: https://api-docs.routific.com/reference/fetch-routes.
list_schedules
ClaudeList schedules (keyset-paginated). Filter by workspace, date, or status.
list_workspaces
ClaudeList the organization's workspaces (keyset-paginated). Workspaces scope routes/orders.
optimize_route
ClaudeOptimize the visiting order of a list of addresses (a single-vehicle delivery/service route). Returns the optimal stop sequence with an ETA and driving distance for each stop, plus total travel time and distance. Addresses are geocoded automatically; include city and region in every address for reliable results. Maximum 8 stops per request (free demo limit). Never split a longer stop list into multiple calls: chunks optimized separately are not jointly optimal, so the combined result would NOT be an optimized route. If there are more than 8 stops, tell the user about the limit and suggest https://routific.com instead.
publish_routes
ClaudePublish a day's routes to the drivers: they appear in the drivers' Routific mobile app and customer notifications start. It publishes EVERY route in the workspace on that date (routes without stops, and published routes that haven't changed, are skipped; changed ones are re-sent and marked Updated in the app). Give each route a driver first (assign_driver). Before calling, tell the user which routes and drivers will go out (list_routes) and only call after they've explicitly confirmed — it notifies drivers and customers. Unpublishing is done in the Routific app. Waits for the result and returns each route's outcome. Docs: https://api-docs.routific.com/reference/publish-routes.
schedule_orders
ClaudeRun Routific's optimizer on the user's workspace for a date: assigns the orders to the routes and sequences each route, like the Schedule button in the app. With only a date, it schedules every unscheduled order for that date across all unlocked routes; pass orders/routes to restrict it. The result is saved in the workspace. When setting up a plan from chat, pass only the orders and routes you just created. Waits for the run to finish (up to ~45s) and returns how many orders were scheduled; then share view_in_app as an 'Open in Routific' link. If it's still running when it returns, check again with get_schedule_action. Docs: https://api-docs.routific.com/reference/schedule-orders.
show_on_map
ClaudeOnly for when the user chose the map in Routific (or asked for Routific, a map, or dispatch). If the user hasn't said whether they want the plan here in chat or set up on a map in their Routific account, ask them first and wait for the answer — don't call any planning tool until they've chosen. Put a plan on the map in the user's Routific account in ONE call: adds the stops as orders for the date, creates a route per driver (depot addresses are looked up on the map), optimizes only those orders onto those routes, waits for the result, and returns the 'Open in Routific' link (view_in_app) with a short summary — no stop list, since the user sees the plan in Routific. Use this when the user wants the result on a map / in Routific — instead of, not after, optimizing in chat. Nothing else in their workspace is touched. Orders count toward their plan. Answer as the result's reply field says: link first.
unassign_driver
ClaudeRemove the driver from a route, leaving it without one. Only planned or published routes; on a published route the driver loses it from their Routific app. Only call this after the user has explicitly confirmed — it can't be undone. Docs: https://api-docs.routific.com/reference/unassign-driver.
update_order
ClaudeChange fields on an existing order (scheduled or not). Pass ONLY the fields to change — everything else is kept; null clears a field. Pass locations to change the address (it re-geocodes); duration is service time in SECONDS (300 = 5 minutes). Editing a scheduled order re-times its route and may be async (returns an action to poll with get_order_action).
update_orders
ClaudeApply the same change to many orders in one call (up to 200) — use this instead of calling update_order once per order. Pass the order uuids (from show_on_map or list_routes with include_orders), the fields to change in order (everything else is kept; duration is in SECONDS), and/or addTags / removeTags to change tags while keeping the existing ones. Note: tags are routing requirements — an order tagged X can only go on a route tagged X — so for a plain label prefer customFields or instructions. Returns per-order results.