What was agreed on WhatsApp,
reconciled with your records.
Your own Claude or Codex reads WhatsApp through TradeNodus, and your shipment sheet through the spreadsheet connector you already have. It lists each difference with the message that proves it. You confirm, and it updates the row.
| Contract | Seller | Qty | Vessel | ETD | BL date | |
|---|---|---|---|---|---|---|
| 12 | COF-025 | Santos Brokers | 240 MT | MV Nordic Star | 28 Oct | 28 Oct |
| 13 | COF-026 | Azimut | 160 MT | MV Baltic Wren | 31 Oct | 31 Oct |
| 14 | COF-027 | Azimut | 320 MT | MV Atlantic | 4 Nov | |
| 15 | COF-028 | Azimut | 80 MT | |||
| 16 | ||||||
| 17 |
Does your sheet match WhatsApp?
One question, asked in your own assistant: “Does the COF-027 row match what the forwarder confirmed this week?” COF-027 is a sample trade. The film has no sound.
Set up once, then ask.
It works in Claude, Claude Code and Codex. TradeNodus gives your assistant the WhatsApp side. Your own connector gives it the sheet.
- Chats to keep3 of 4
- FSFreight & Shipping
- ASAzimut Supplier
- SBSantos Brokers
- FAFamily
- Your assistantConnectors
- TradeNodusWhatsApp, read-onlyConnected
- Spreadsheet connectorExcel or Google SheetsConnected
Yes, update the row.
Shipments 2026UpdatedContract ETD BL date 14 COF-027 4 Nov9 Nov 9 Nov
What it catches.
The changes that arrive on WhatsApp and never reach the sheet.
- Elena BrandtCOF-023 now sails 6 Nov1.09:12
ETD 10 2 Nov1 A vessel or ETD change
The forwarder moves the sailing. The sheet keeps the old date.
- Elena BrandtBL for COF-021 dated 3 Nov2.11:40
BL date 8 2 A BL date
Given in the group, blank in the sheet. The LC presentation deadline moves with it.
- Jorge RuizCOF-022 confirmed at 340 MT3.14:05
Qty 9 320 MT3 A quantity or a price fixation
A new tonnage or a fixed price, agreed in the chat and not yet entered.
- Elena BrandtCOF-026: originals couriered to the bank4.16:22
Docs sent 13 4 A document the forwarder says was sent
“Originals couriered to the bank” in the chat, and no date for it in the sheet.
Your chats stay with you.
You choose what is kept and who reads it, and you can take it back.
Only the chats you tick.
The bridge keeps sender, time and text from the chats your desk ticks, and nothing from the rest. Your assistant sees only those, and only what it asks for.
Your firm’s own instance.
One bridge and one database per firm, on servers at Infomaniak in Switzerland, encrypted at rest.
Read by people you let in.
Colleagues sign in with their work email. Anyone new waits until an approver at your firm lets them in.
Nothing goes back.
It cannot send messages, read receipts or “online”. It cannot open or change your sheet.
Leave at any time.
Untick a chat and its messages are deleted. Unlink it on your phone and it is cut off at once. When your firm leaves, we delete its instance.
We run the server, so we could technically read what it holds while it runs. We don’t. To rule it out, run the bridge on your own machine. Read the privacy notice.
Give your assistant the WhatsApp side.
Access is by invitation, one firm at a time. New to TradeNodus? Request access below. Already on it? Sign in at your firm’s address with your work email; an approver lets new people in.
Request access.
TradeNodus is in pilot. Tell us what your desk trades, which chats matter and where your shipment sheet lives. We set up your firm’s own instance in Switzerland and invite the first person by email.
Hosted in Switzerland. Each firm’s bridge runs on its own instance at Infomaniak, in Switzerland, with its database encrypted at rest. Your sheet stays where it is.