Connected operations

Connected to the systems
your operations already run on.

Your TMS is the starting point—whether it’s a commercial platform or built in-house. Shipflow connects the work around it, from email and customer context to market-rate data and internal tools.

Discuss your stack Using an in-house system?

Explore connection opportunities by category. Products marked “Scope to confirm” require validation of the connection, account access and supported actions; listing a product does not imply a native connector or partnership.

02 · Where operational requests begin

Email

Bring messages, attachments and replies into a structured workflow. Keep reading, drafting and sending permissions distinct.

Email & shared inboxes

Microsoft 365 Outlook

Connect Outlook requests and attachments to quotation, documentation and controlled follow-up workflows.

Scope to confirmExplore Outlook

Google Workspace email

Gmail

Scope email intake, attachment handling and response preparation around the mailboxes your team authorizes.

Scope to confirmExplore Gmail

03 · Keep customer context with the work

CRM

Connect customer requests and follow-ups with the commercial context your team needs. Agree on record matching and update permissions before execution.

Customer & opportunity context

HubSpot

Scope how contacts, companies and opportunity context support customer inquiries, quotation follow-ups and operational handoffs.

Scope to confirmExplore HubSpot

Dataverse & CRM workflows

Microsoft Dynamics 365

Connect customer context, follow-up activities and service handoffs through scoped Dynamics 365 CRM access.

Scope to confirmExplore Dynamics 365

Customer & sales operations

Salesforce

Connect account and opportunity context to quotation preparation, customer service and tender follow-ups.

Scope to confirmExplore Salesforce

Sales & service workflows

SAP C/4HANA

Scope customer-facing workflows against the actual SAP Sales or Service Cloud product, version and API in use.

Scope to confirmExplore SAP C/4HANA

04 · Pricing context for the next decision

Market Rate Source

Bring relevant rate data into quotation, tender pricing and carrier-rate review. Keep market benchmarks distinct from shipment-specific offers and contract rates.

Market benchmarks

Freightos

Scope Freightos Terminal market benchmarks as context for quotation reviews, tender comparisons and pricing decisions.

Live & contract-rate inputs

WebCargo

Scope relevant live or contract-rate inputs from WebCargo, now Freightos for Forwarders, for comparison within your pricing workflow.

Scope to confirmExplore WebCargo

Freightos and WebCargo have separate guides: market benchmarks and shipment-specific rate inputs serve different purposes. Data products, credentials and access rights are not interchangeable.

Custom-built & in-house systems

Built in-house? Bring it into the workflow.

Shipflow integrates with custom-built and in-house systems—not just off-the-shelf software. Connect your proprietary TMS, internal operations tools and customer portals to AI Operators without replacing the systems your team relies on.

Discuss your in-house system
Connect through approved interfaces
Use available APIs, approved data interfaces or existing middleware. If an API is not available, we assess alternatives with your engineering team before agreeing on the approach.
Keep your SOPs and permissions
Define which records an AI Operator can read or update, when human approval is required and how exceptions reach the right person.
Validate before going live
Confirm interface availability, access controls and supported actions with your system owner, then test the agreed workflow before production rollout.

Implementation ready

A practical path from your stack to live automation.

Our team maps the systems, data and workflow controls that matter to your operation—then deploys Shipflow alongside them.

01

Workflow and system mapping

Map the systems, data and decision points involved in the operation you want an AI Operator to execute.

02

Controlled, secure data access

Give each operator access only to the information and actions required for its defined workflow.

03

Custom connections when needed

Connect APIs, inboxes, documents and portals around the systems your operation already depends on.