Automation · Orders and fulfillment
Quote a Chilexpress shipment over WhatsApp
An AI agent quotes a Chilexpress shipment over WhatsApp using coverage, weight and dimensions, then returns the list-rate options from Chilexpress.
How do I quote a Chilexpress shipment over WhatsApp without calculating the rate myself?
A Met connected to Chilexpress first checks that the Quote product has its own key and whether a default origin commune is configured. It resolves the origin and destination commune codes, asks when a match is ambiguous, and checks coverage without credentials. If the customer provides an address, it separates street, number and supplement but does not claim the place exists. With destination, weight and, when available, dimensions and declared value, it asks Chilexpress for a quote. It communicates each `serviceValue` in Chilean pesos exactly as returned, along with the service and final billable weight. It never computes or interpolates a price. The result is a list rate that excludes discounts and special agreements, and the query creates no transport order, tracking number, label, pickup or shipment.
Where it applies: Chile. Region and commune codes, CLP currency and coverage in this recipe belong to Chilexpress's domestic operation in Chile.
What starts it
When the customer writes
It starts when someone asks over WhatsApp what it costs to send a parcel with Chilexpress and provides, or agrees to complete, the origin, destination and weight. It is not scheduled and does not run without a concrete question in the conversation.
Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.
Who runs it
Commercial support Met
This is not a named, seeded Met. It is the same Met already handling your WhatsApp with Chilexpress connected. Its job here ends after resolving coverage and returning the carrier's options. It does not turn a price query into a transport order.
Channels: WhatsApp
What you need connected
- Chilexpress Run stores and orders
5 steps · 6 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
Check the connection before requesting a rate
The Met checks the active environment, whether the Quote product key is configured, and whether the workspace already has a default origin commune. This query does not touch the network or change configuration. If the key is missing, it can still resolve communes and coverage, but stops before promising a price because quoting requires that specific key.
- 2
Resolve communes without choosing for the customer
It searches the destination by name and also the origin when no default is configured. The result includes the four-letter Chilexpress commune code. If several matches appear, the Met shows commune and region and asks which one applies. Only when the region helps narrow the result does it list official region codes and search again with the selected region. It never picks the first match just to move on.
- 3
Check destination coverage
With the confirmed commune code, it checks whether the destination is in the coverage registry. This works even when no key is configured. A covered result allows the quote to continue, but does not equal a rate or authorize the Met to interpret internal indicators as a promise about the delivery method.
- 4
Split the address only when the customer provides it
If the conversation already includes an address, the tool splits and standardizes street, number and supplement, and reports a missing number. This is optional and the quote does not consume the address. It does not check a street catalog or validate that the property exists. If the customer only wants a price for a commune and parcel, the Met skips it.
- 5
Request real options from the Quote API
The Met sends the configured or confirmed origin code, destination and a weight above zero. Dimensions and declared value are optional for the tool; when the team has them, it passes them without filling gaps with assumptions. Chilexpress resolves volumetric weight and returns the options. The Met replies with the service, conditions, final billable weight and each `serviceValue` in CLP exactly as returned. If there are no options, it says there is no rate for those inputs and does not manufacture an average or interpolate another lane.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
A Chilexpress Quote product key
Subscribe to the Quote product in the Chilexpress developer portal, then configure the key in the workspace. It is separate from other portal keys. Commune search and coverage do not need it, but requesting a rate does.
-
A confirmed origin or a configured default
You can save the four-letter commune code as the connector's default origin. If it is not set, the Met asks for the commune name, resolves its code and asks you to confirm every ambiguous match before quoting.
-
Destination and actual parcel weight
The customer provides the destination commune and your team knows or weighs the parcel in kilograms. Dimensions in centimeters and declared value in CLP are optional for the tool. When available, they are sent because Chilexpress uses them when returning options and billable weight.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not create a transport order, tracking number or label. It does not schedule a pickup, book a collection or register a shipment. Every tool in this recipe is read-only.
-
It does not calculate, average or interpolate prices. It only communicates the `serviceValue` of an option returned by Chilexpress. If the Quote API returns no option, there is no rate to invent.
-
It does not apply discounts or commercial agreements. The Chilexpress portal defines the Quote API result as a list rate without customer discounts or specially agreed rates.
-
It does not choose an ambiguous commune. When search returns more than one match, it asks for the correct commune and region before checking coverage or price.
-
It does not validate that an address exists or compare it with an official catalog. It only splits and standardizes the text into street, number and supplement. That address is not even part of this recipe's quote request.
-
It does not compute volumetric weight. Chilexpress decides the final billable weight and the Met explains the fields returned by the Quote API without rebuilding the formula itself.
FAQ
Questions about this automation
No. Region and commune lookup and coverage queries work without credentials in this connector. Returning priced options does require the specific Quote product key.
No. The official portal states that the Quote API returns list rates and does not include customer discounts or specially agreed rates. The Met labels it as a list rate, not the final amount under your agreement.
The Met shows the matches with their region and asks which one is correct. If a region can narrow the result, it gets the region code and searches again. It never selects a commune by result order.
The connector requires destination and weight. Height, width, length and declared value are optional. When available, provide them because Chilexpress uses those inputs when returning its options and final billable weight. The Met does not invent missing dimensions.
No. That tool only splits and standardizes the text into street, number and supplement, and reports a missing number. It does not search the Chilexpress street catalog or certify that the address exists. The quote endpoint does not receive that address either.
No. The recipe has no mutations and ends after presenting the options. It creates no transport order, tracking number, label, pickup, collection or shipment, even if the customer chooses one of the rates.
Keep going
Other automations built on the same tools
Orders and fulfillment
Accept, prepare and close Rappi orders without living on the tablet
How do I stop losing Rappi orders because nobody accepted them in time?
- Starts:
- when the outside system calls
- Steps:
- 6, with 10 real tools
- Needs:
- Rappi
Orders and fulfillment
Quote a TCC shipment from WhatsApp
How do I quote a TCC shipment from WhatsApp?
Finance and operations
- Starts:
- when the customer writes
- Steps:
- 5, with 8 real tools
- Needs:
- TCC · Meteor CRM
Orders and fulfillment
Create a Shopify order over WhatsApp for cash on delivery
How do I take a Shopify order over WhatsApp and leave it marked for cash on delivery?
- Starts:
- when the customer writes
- Steps:
- 5, with 7 real tools
- Needs:
- Shopify
Orders and fulfillment
Create a WooCommerce order over WhatsApp for cash on delivery
How do I create a WooCommerce order over WhatsApp and mark it for cash on delivery?
- Starts:
- when the customer writes
- Steps:
- 5, with 8 real tools
- Needs:
- WooCommerce
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.