Connect Claude & ChatGPT to Locate2u

28 tools for Locate2u

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_stop_noteChanges dataAdd a note to a stop by `stop_id` with `note` text.
• change_stop_statusChanges dataChange a stop's status by `stop_id` with `new_status`: Pending, Enroute, Delayed, Arrived, Departed, Complete, Cancelled, OnHold, Failed or Unrouted.
• create_customerChanges dataCreate a customer with name or first_name/last_name, company, email, phone, address and notes. Search first to avoid duplicates.
• create_orderChanges dataCreate an order with contact, delivery details, contents, load and notes. Search first to avoid duplicates.
• create_shipmentChanges dataCreate a shipment with a `pickup_stop` and `drop_stop`, `trip_date`, `contact`, `customer_id`, `load` and `notes`. Optionally assign both halves with `assigned_to_public_user_id`.
• create_stopChanges dataCreate a delivery or pickup stop. Key inputs: `address`, `type` ("Drop" or "Pick Up"), `trip_date`, `contact`, `customer_id`, time window (`time_window_start`/`time_window_end` like 09:00), `duration_minutes`, `notes` and optional `assigned_team_member_id`.
• delete_stopDeletesPermanently delete a stop by `stop_id`. Cannot be undone.
• find_stops_by_referenceFind stops by the `source_reference` you set when creating them.
• get_current_userGet the connected Locate2u user's profile and team.
• get_customerGet one customer by `customer_id`.
• get_orderGet one order by `order_id`, with its contact, contents and delivery details.
• get_shipmentGet one shipment by `shipment_id`, with its pickup and drop stops and optionally tracking link and cost lines.
• get_shipment_quoteChanges dataGet a price quote for a shipment from `pickup_address` to `drop_address` with weight, volume, quantity and `trip_date`. Does not create anything.
• get_stopGet one stop by `stop_id`: address, status, time window, assigned driver and optionally its lines and tracking link.
• get_team_memberGet one team member by `public_user_id`.
• get_team_member_tripGet one team member's trip for a `trip_date` by `public_user_id`, optionally filtered by `status`.
• list_scheduled_stopsList stops scheduled for a `trip_date` (YYYY-MM-DD), optionally in one `team_region_id`. Paged with `take` and `offset`.
• list_stop_notesList notes and messages on a stop by `stop_id`.
• list_team_membersList team members (drivers) with their public user IDs, optionally in one `team_region_id` and with current location.
• list_team_tripsGet every team member's trip (route) for a `trip_date` (YYYY-MM-DD), with stops in order and progress.
• list_unassigned_shipmentsList shipments (pickup plus drop pairs) not yet assigned, optionally for a `trip_date` or `team_region_id`.
• list_unassigned_stopsList stops not yet assigned to a team member, optionally for a `trip_date` or `team_region_id`.
• optimise_tripsChanges dataRe-optimise the stop order of trips on a `trip_date` (YYYY-MM-DD). Drivers' routes change; set `lock_trip_after_optimisation` to lock them afterwards.
• search_customersSearch customers by `search_text` (name, email, phone). Use this to find a customer ID before creating stops or orders.
• search_ordersSearch orders by `order_number`, `customer_id`, `status`, `payment_status` or `order_date`. Paged with `page` and `orders_per_page`.
• update_customerChanges dataUpdate a customer by `customer_id`; pass the fields to change such as email, phone, address or notes.
• update_shipmentChanges dataUpdate a shipment by `shipment_id`: contact, load, notes, pickup/drop details or assignment.
• update_stopChanges dataUpdate a stop by `stop_id`: address, contact, time window, notes, trip date or assigned team member.

Questions