Using Dockflow in Gemini Enterprise
The Dockflow connector for Gemini Enterprise lets you ask about your containers in the chat, using your own Dockflow account.
Gemini Enterprise connects to Dockflow as a custom MCP server. An administrator of your Gemini Enterprise app adds it once; after that, each user signs in with their own Dockflow account.
Adding the connector (administrator)
You need the Discovery Engine Editor role on the Google Cloud project of your Gemini Enterprise app. If your organisation restricts custom MCP data stores or outbound domains, allow mcp.dockflow.com and core.dockflow.com.
- In the Google Cloud console, open your Gemini Enterprise app and go to Connected data stores.
- Select New data store, then Custom MCP Server.
- Choose OAuth 2.0 as the authentication and enter:
| Field | Value |
|---|---|
| MCP server URL | https://mcp.dockflow.com/mcp |
| Authorization URL | https://core.dockflow.com/o/authorize/ |
| Token URL | https://core.dockflow.com/o/token/ |
| Client ID | dockflow-gemini |
| Client secret | Ask your Dockflow contact person or [email protected] |
| Scopes | read |
Leave Use HTTP Basic Authentication switched on.
- Name the data store Dockflow and finish the setup.
- Under the data store's actions, enable all Dockflow actions.
- Make sure the data store is connected to your Gemini Enterprise app.
Connecting your account (every user)
- In Gemini Enterprise, open the Dockflow connector and select Authorize.
- Sign in with your Dockflow account.
- Approve the access request.
You only do this once.
Asking a question
Once connected, ask about a container by number:
- "Where is container MSCU1234567?"
- "When does MSCU1234567 arrive?"
- "Has MSCU1234567 been discharged yet?"
If Gemini does not reach for Dockflow on its own, name it in the question: "Ask Dockflow where MSCU1234567 is."
Give the full container number, or at least its first four characters.
What you get back
For every match, the answer can include:
| Field | What it is |
|---|---|
| Container number | The full container number, with its size and type |
| Tradeflow | The tradeflow the container belongs to, its reference, and a link to it in Dockflow |
| Ports | The port of loading and final port of discharge, plus any transshipment ports |
| Vessel schedule | Estimated departure from the port of loading and arrival at the port of discharge |
| Milestones | Gate in, loaded, departed, arrived, discharged, gate out, delivered and empty return, each marked as happened or expected |
Times are shown in the local time of the place the event happened, with its UTC offset. A load in Gebze reads 09:36 (+03:00); an arrival in Antwerp reads 18:00 (+02:00). One container can show several offsets, one per port, so read the offset along with the time.
If the same container sits on more than one tradeflow, you get one result per tradeflow. That is correct, not a duplicate.
Limits
- It does not edit your tradeflows. It reads tracking data. The only thing it creates is an ocean booking, and a booking only goes to the carrier when you submit it.
- Your own access only. You see the tradeflows your Dockflow account can already see. Connecting does not change your permissions.
- Gemini Enterprise only. The Gemini that comes with a Google Workspace subscription cannot connect to Dockflow.
If it does not find your container
- Check the container number for typos.
- Open Dockflow and confirm the container is visible to your account. If it is not visible there, the connector cannot see it either.
- If it is visible in Dockflow but the connector cannot find it, contact your Dockflow contact person or raise a ticket.
Privacy and terms
The connector signs you in with your own Dockflow account. Your Dockflow password is never shared with Google.
See the Privacy Policy and the Terms of Service.