Show the TrackFlo Assignee in Front

TrackFlo exposes one lookup for Front: given a shipment id, it returns the assignee's email, the latest update and the reps on the load, so a Front rule or plugin can route or annotate the conversation.

What you need from TrackFlo

• A Front Integration API key for your tenant. Ask TrackFlo; it is issued from the API keys page with type Front Integration and shown once.

• Your tenant slug (company_permalink), e.g. acme. The key is bound to it; you do not need to send it.

The request

GET https://integration-api.trackflo.tech/api/v1/get-assignee?shipment_id=1083452
X-API-Key: <your Front Integration key>

Alternative lookups when you do not have the shipment id: bol_number=<…> or customer_ref_number=<…>.

The response

{
  "shipment_id": "1083452",
  "assignee_email": "[email protected]",
  "latest_load_update_comment": "Departed shipper, on time",
  "latest_location_city": "Austin",
  "latest_location_state": "TX",
  "carrier_account_manager_name": "…",
  "carrier_account_manager_email": "…",
  "carrier_sales_rep_name": "…",
  "carrier_sales_rep_email": "…",
  "customer_account_manager_name": "…",
  "customer_account_manager_email": "…",
  "customer_sales_rep_name": "…",
  "customer_sales_rep_email": "…"
}

404 Load not found when nothing matches. 401 for a missing or unknown key.

Setting it up in Front

1. In Front, create (or edit) the rule or plugin that calls TrackFlo.

2. Set the request URL to the endpoint above with shipment_id taken from the conversation.

3. Add a header X-API-Key with the key TrackFlo issued.

4. Remove any token= query parameter from an older configuration. It is no longer accepted: a request without X-API-Key returns 401, whatever the query string contains.

5. Send a test conversation and confirm the key's Last used time moves on TrackFlo's API keys page.