Integration · Shipping and logistics
TCC and Meteor AI agents
Connect TCC to Meteor: quote shipments, track waybills and explain exceptions over WhatsApp. Read only, with 13 real tools.
How does TCC connect to Meteor?
Meteor connects to the Colombian carrier TCC so your Met can quote a shipment at your real contract rate, track one waybill or many, explain what an exception means and who it is attributable to, and confirm whether TCC reaches a town and whether that town allows cash on delivery. These are 13 read only tools. The connector does not create dispatches, does not request pickups and does not void waybills. If you need the dispatch actually completed, the Aveonline connector is the one we recommend.
Where it applies: Colombia. The connector ships with the local master list of Colombian towns and their DANE code, to disambiguate identical names before quoting.
What it automates
What a Meteor Met does with TCC
Answer where my order is in seconds
The customer sends their waybill number and your Met answers with the tracking history, the status translated into plain language and the promised delivery date, with nobody opening the portal.
Quote the shipment before closing the sale
Your Met resolves the destination town code, quotes against your commercial agreement and answers the real shipping cost, with the billed weight the carrier applied.
Explain an exception instead of repeating it
When a shipment hits an exception, your Met says who it is attributable to and what comes next. Asking the customer for their address is not the same as apologizing and escalating internally.
Offer cash on delivery only where it exists
Before promising cash on delivery, your Met checks whether that town allows it. It is the promise most often broken when it is made from memory.
13 tools
Everything your Met can ask TCC for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
tcc_cotizar_envio | A real shipment quote, with itemized charges, billed weight and promised transit days. |
tcc_consultar_tarifas | Returns the reference rate table for an origin and destination pair. It is not a quoting engine. |
tcc_rastrear_envio | Tracks a waybill with its history, its exception and the delivery details. |
tcc_rastrear_multiples | Tracks several waybills in one call, instead of looping the same query. |
tcc_consultar_envio | The full shipment record: weights, freight, cash collection, promised date and parties. |
tcc_informacion_remesas | Lightweight tracking for many waybills at once, when all you need is the status. |
tcc_consultar_novedad | Explains an exception and says whether it is attributable to the carrier, the customer or a third party. |
tcc_consultar_estado | Translates a status code into what it means and flags the critical ones. |
tcc_buscar_ciudad | Finds a town in the local master list and returns its DANE code, disambiguating identical names. |
tcc_consultar_cobertura | Says whether TCC reaches a town and under what conditions. |
tcc_ciudades_con_fce | Lists the towns that allow freight on delivery with cash collection. |
tcc_validar_direccion | Normalizes a Colombian address for dispatch, expanding street type abbreviations. |
tcc_consultar_conexion | Verifies the token is configured and reports the active environment and commercial account. |
The limits
What the TCC integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not create waybills and it does not record dispatches. It does not request pickups and it does not void waybills. This integration is read only. For a connector that finishes the dispatch, use Aveonline.
-
It does not calculate the price or the billed weight on its own. It returns what the carrier answers, unchanged, because freight computed locally is freight invented.
-
It does not validate addresses against an official catalog. The carrier does not expose that check over the API, so the connector only standardizes the address text.
-
It does not return the proof of delivery image. It returns the link, never the embedded file.
Before you start
What you need to connect TCC
- 1
A TCC API access token
TCC provides it. The test token and the production token are different, and you declare the environment when configuring the integration.
- 2
Your commercial agreement number
It is your contract number with TCC. It is required to quote, because the rate depends on the agreement and not on a public list.
- 3
Origin city and business unit (optional)
Configured once with the code of the city you usually ship from and the service mode (parcel or courier), so you do not repeat them on every query.
Frequently asked questions
Questions about TCC and Meteor
Not yet. This integration quotes, tracks and explains statuses and exceptions, but it does not write to the carrier: no dispatches recorded, no pickups requested, no waybills voided. When the dispatch has to end up done, the Aveonline connector is the one we recommend.
It is the real one. It is requested against your commercial agreement and returned with itemized charges and the billed weight the carrier applied. The rate table by origin and destination pair exists separately and is reference only.
With the local master list of towns and their DANE code. Colombia has three towns called Rionegro, and the connector forces you to disambiguate instead of choosing on its own.
Yes, in two ways: a batch lookup with the full detail, and a lightweight tracking call for when you only need the status of many waybills at a glance.
Step by step
Automations that use TCC
Complete tasks, with the steps and the tools that run at each one.
Shipping and logistics
Other integrations in the same family
Want to see a Met running TCC?
We will show you with your own account connected, not with a canned demo.