Booking request intake
Extract an incoming request and its attachments, identify missing fields and match existing work before preparing a booking handoff to the authorized system.
Explore this workflowAI Operators · Email
Shipflow for Gmail
Turn authorized Gmail messages and attachments into logistics workflows. Explore Google Workspace access, mailbox updates, reply controls and TMS handoffs.
Workflow-specific integration. Shipflow connects to Gmail through approved APIs, secure account access, file exchange or existing middleware—using the connection route that fits your environment and workflow.
Discuss your Gmail workflowYour systems. Your SOPs.
- Mailbox scope
- Named Google Workspace mailboxes and operational owners.
- Vendor API
- Gmail REST API, OAuth scopes and optional Pub/Sub mailbox notifications.
- Human control
- Message access, response preparation and sending governed by separate operating rules.
Where integration creates value
Turn inbox activity into accountable operational work.
A logistics inbox mixes new requests, forwarded messages, revised attachments and carrier replies. An AI workflow needs to determine what changed and which job it concerns before it can safely prepare a booking, compare a document or follow up on a quotation.
Shipflow turns Gmail requests and replies into the next operational step. Mailbox access remains separate from Drive, CRM and TMS permissions; each system keeps its own access controls.
Workflow opportunities
Start with the work you want to complete.
Document revision handling
Associate a message and attachment version with the correct shipment. Compare required fields and route discrepancies with source context.
Explore this workflowQuotation and reply coordination
Gather the request, approved pricing inputs and relevant replies. Prepare a clarification or customer response under the sender, recipient and approval rules your team defines.
Explore this workflowIllustrative workflow
From a Gmail request to an approval-ready response
Illustrative workflow: a customer sends an incomplete quotation request and later replies with revised cargo information.
Identify the conversation
Resolve the message and thread, detect duplicates and associate the request with the intended operational case.
Interpret the latest requirements
Compare the reply and attachment versions with the prior request. Do not treat quoted old content as a new instruction.
Prepare the next response
Gather authorized context and draft a clarification or quotation response. Keep unsupported prices and assumptions out of the message.
Release within policy
Obtain review where required, confirm sender and recipients, and send only if authorized. Track the actual result before attempting a retry.
Connection approach
Available connection routes.
The Gmail API supports mailbox access through OAuth scopes. Read, compose and send scopes differ; importantly, gmail.compose includes both draft management and sending. A draft-only operating policy therefore needs an application-level control, not just a claim that the scope prevents sending. Google classifies some mail scopes as restricted, so review applicable verification and security-assessment requirements.
For server-side mailbox changes, Google documents watch notifications through Cloud Pub/Sub. Notifications signal changes rather than delivering the complete email; the consumer retrieves the relevant mailbox history and messages. Renew watches and reconcile delayed or missed events. Do not promise that every message is delivered instantly or exactly once.
Setup requirements
What the first deployment needs.
Mailbox and administrator approval
Confirm the actual mailbox, owner, Workspace policy and OAuth authorization. An alias or Google Group should not be assumed to be an independent Gmail mailbox.
Minimum scopes and data policy
Identify required message content and actions, storage limits and the applicable app-verification requirements.
Notification and recovery setup
If push is selected, configure Pub/Sub access, watch renewal, history reconciliation and duplicate suppression.
Sending and handoff rules
Define approved senders, recipients, review conditions and the separately authorized TMS or CRM connection.
Control and rollout
Make access and accountability explicit.
Treat messages as external input
Email content cannot change the operator’s permissions, redirect sensitive information or override your SOP.
Make review a real release boundary
Prevent automatic send actions when a response is awaiting approval, even if the underlying credential technically permits sending.
Reconcile repeated or missing updates
Use message references and processing state to avoid duplicate work and recover requests missed during an interruption.
Common questions
Gmail integration questions.
Can Shipflow use our Google Workspace email?
Yes. Shipflow connects to the named Google Workspace mailboxes your team authorizes, with read, draft, send and notification actions configured separately around your workflow and organizational policy.
Does Gmail compose access prevent sending?
No. Google documents sending within the compose scope. Draft-only behavior must be enforced by the workflow’s application controls and approval process.
Does this grant access to every mailbox?
No. Scope named mailboxes and the approved authorization model. Do not assume domain-wide access or expand access automatically when a mailbox is unavailable.
Can the first workflow avoid sending entirely?
Yes. Start with intake, classification or approval-ready drafts, and verify that no external message is released without the required authority.
Third-party product names belong to their respective owners. Available interfaces vary by product edition and account permissions.
Start with one workflow
Bring your workflow.
Keep your Gmail environment.
Define the first workflow, required system access, controls and acceptance criteria with Shipflow.
Book a working session