booking_add_document
ChatGPTAdd a draft document to a booking. Nothing goes to the carrier. Args: booking_id: The booking part: si (shipping instructions), vgm (verified gross mass), amendment or cancellation fields: Details by part, all optional on a draft. si: transport_document_type (BOL, SWB), is_electronic, is_to_order, freight_payment_mode, parties, equipments, description_of_goods, marks_and_numbers. vgm: container_number, weight_kg, method (SM1, SM2), weighed_at, authorized_person, responsible_party. amendment: the same fields as booking_create. cancellation: reason. Returns: The document: id, part, submission_state, fields, approved_at, created_at. `part_not_available` means the route cannot carry this part.
booking_approve
ChatGPTRecord a person's approval of a booking document. An approval states that a person has seen these values and confirmed them, so this tool is for after the user confirmed the values in the conversation. Nothing goes to the carrier, and a later edit clears the approval. Args: submission_id: The document, from the booking's submissions Returns: The document: id, part, submission_state, fields, approved_at, created_at.
booking_carriers
ChatGPTCarriers that can be booked with, and what each route can carry. Returns: `{"results": [...]}`, each with scac, name, needs_agreement_reference, unattended, and routes. Each route has route ("direct" or "web"), parts (booking, si, vgm, amendment, cancellation), connected and is_default.
booking_create
ChatGPTCreate a booking draft at a carrier. Nothing goes to the carrier. Args: carrier_scac: Four-letter carrier code from booking_carriers route: Route from booking_carriers. Null uses the entity's default route, or the only route a carrier has. idempotency_key: A repeated key returns the original booking fields: Booking details, all optional on a draft: agreement_reference, receipt_type_at_origin and delivery_type_at_destination (CY, SD, CFS), port_of_loading and port_of_discharge (UN/LOCODE), place_of_receipt, place_of_delivery, departure_date, vessel_name, voyage_number, carrier_routing_option, freight_payment_mode (prepaid, collect), remarks, parties (role, name, address_lines, carrier_party_code, contact_email) and equipments (iso_equipment_code, units, is_shipper_owned, container_numbers, commodity_code, commodity_description, hs_codes, cargo_gross_weight_kg, reefer). Returns: The booking: id, idempotency_key, carrier_scac, route, status, source, created_at, updated_at, events, and submissions holding the booking document with its id, part, submission_state and fields. An error carries `error`; a field error names the field.
booking_get
ChatGPTOne booking with its documents (submissions) and its event history. Returns: id, idempotency_key, carrier_scac, route, status, source, created_at, updated_at, submissions (id, part, submission_state, fields, approved_at, created_at) and events (kind, submission_id, detail, created_at).
booking_list
ChatGPTBookings of the signed-in user's company. Args: limit: Maximum number of bookings (default 50, 1 to 200) Returns: `{"results": [...]}`, each with id, idempotency_key, carrier_scac, route, status, source, created_at and updated_at.
booking_submit
ChatGPTSubmit a booking document to the carrier on the booking's route, after checking that it is complete, that the route can carry it and that it is approved. Args: submission_id: The document, from the booking's submissions Returns: The document when it was accepted, otherwise an object whose `error is one of: - carrier_credentials_missing: nothing was sent, as the account holds no credentials for this carrier. Also has message, carrier_scac, route, submission_id and console_url, the page to add them. - submission_incomplete: problems lists each field and its message. - approval_required: no person has approved this document yet. - route_required: routes` lists the routes to choose from. - part_not_available: the route cannot carry this part.
booking_update_document
ChatGPTReplace all fields of a booking document with the given ones. This returns the document to draft and clears any earlier approval. Args: submission_id: The document, from the booking's submissions fields: The complete set of fields for that document's part Returns: The document: id, part, submission_state, fields, approved_at, created_at.
search_containers
ChatGPTSearch for containers by container number. Searches across all tradeflows the user has access to. Admin users can see all containers across all entities. Note: The same container can appear multiple times if it's linked to multiple tradeflows. Args: query: Container number or partial container number to search for limit: Maximum number of results to return (default: 50, max: 100) Returns: List of matching containers with comprehensive info: - container_number: Full container number - tradeflow_id: Associated tradeflow ID - tradeflow_reference: Tradeflow reference number (entity-specific) - pol_name: Port of loading name - etd_pol: Estimated departure date from POL - pod_name: Final port of discharge name - eta_pod: Estimated arrival date at POD
search_shipments
ChatGPTFind active shipments by situation instead of by container number, using the same checks as the operations power dashboard. Checks (combinable; two checks that set the same filter differently are refused): - vessel_arrived_24h / vessel_departed_24h / created_24h: happened in the last 24 hours - arriving_tomorrow / arriving_7d / arriving_14d: ETA in that window, not yet arrived - departing_7d: ETS in the next 7 days, not yet departed - at_sea: departed, not yet arrived - waiting_for_pickup: discharged at destination, not picked up - picked_up: full gate out at destination, empty not yet returned - arrival_overdue: ETA passed in the last 7 days, not arrived - departure_overdue: ETS passed in the last 7 days, not departed - at_destination_4d: arrived over 4 days ago, still not picked up - at_sea_60d: departed over 60 days ago, still not arrived - without_containers: active tradeflows with no containers - strait_of_hormuz / red_sea: route passes through that sea area Args: checks: Zero or more check ids from the list above query: Free text matched against references, container numbers, bookings and bills of lading carrier / vessel / port_of_loading / port_of_discharge / partner: Text filters on that field level: "tradeflow" for one row per shipment, "container" for one row per container limit: Rows per page (default 25, 1 to 100) page: Zero-based page number Returns: `{"results": [...], "total": int, "total_is_lower_bound": bool}. Each result has kind, tradeflow_id, container_id (container rows), url (deep link into the Dockflow app) and the columns reference, client_reference, containers, booking, bill_of_lading, carrier, vessel, port_of_loading, port_of_discharge, partner, flags and the vessel times ets, ats, eta, ata and etd_pod (estimated departure from POD). Container rows also carry the actual milestones empty_gate_out, full_gate_in, loaded_on_vessel, discharged, full_gate_out and empty_returned, each {"text": place, "at", "timezone"}; the estimate expected_discharge; latest_milestone, the furthest of those milestones (with ats/ata as vessel departure/arrival) reached so far, as {"milestone", "text", "at", "timezone"}; and the import release lights customs_release, terminal_release and commercial_release, each {"text": state, "at", "detail": source and reasons} with state e.g. RELEASED or BLOCKED. at values are UTC instants and timezone` is the IANA zone of the place. ets, eta, etd_pod and expected_discharge are estimates that may change; ats, ata and the milestones record events that already happened. A value with a single field is given bare, a column with several values is a list, and an empty one is null.
track_container
ChatGPTWhere is a shipping container now? Looks the container up with its carrier and returns the latest journey: carrier, ports of loading and discharge, departure and arrival dates (actual or estimated), transshipment ports, vessels per leg, and each container's latest confirmed event. Dates are in the local time of the port. Works for any container number, no account needed. A first ask can take up to a minute while the carrier is checked. When the answer has `status: "checking", ask again in a minute with the same number. found: false` means the carrier does not know the container. A container in your own Dockflow account is answered from it instead.
whats_new_for_me
ChatGPTRecent Dockflow product updates relevant to the signed-in user's company, newest first: what each one does, what changed, where it shows, and a link to its documentation where there is one. unseen is true for an update the user has not yet seen in Dockflow.
booking_add_document
Claudebooking_approve
Claudebooking_carriers
Claudebooking_create
Claudebooking_get
Claudebooking_list
Claudebooking_submit
Claudebooking_update_document
Claudesearch_containers
Claudesearch_shipments
Claudewhats_new_for_me
Claude