Gmail, wired into every client on your caseload.
Connect the Google Workspace mailbox each agent already uses. Client replies thread onto the right case within a minute. Every message you compose inside ImmiIQ leaves from your own Gmail Sent folder so the client sees your real address in the From line and the firm keeps a native paper trail even if it later moves off the platform.
Thanks. Attaching my updated CV and IELTS scorecard.
2 attachmentsGot them. Running the 189 points check and I will confirm your subclass shortlist today.
Sent via your GmailWhat the Gmail integration actually does.
Every capability listed below is live in production today. Nothing on this page is a roadmap promise or a marketing stub.
Two-way message sync
Client replies land on the client timeline whether they reach you inside ImmiIQ or straight in Gmail. Threading and quoted history come through intact so nothing is lost mid-conversation.
Send-through-provider
Outbound composed in ImmiIQ leaves through the Gmail API and is written into your Sent folder with the correct References and In-Reply-To headers. Clients see your real firm address in the From line.
Alt-email chips per client
Attach personal, work and secondary addresses to a single client record. Every reply from any of those addresses still threads onto the same person so nothing splits into duplicate cards.
90-day historic backfill
The moment a mailbox is connected the integration pulls the last 90 days of relevant messages so the case timeline is already populated on day one. No blank state, no manual re-import.
How it works.
Three stages. Connect, configure and then everything else runs itself. Most agents are live inside five minutes.
Connect
Sign in to Google under Settings then Integrations. Google shows you the exact scopes ImmiIQ has asked for. Approve and the connection is live. Your Workspace admin can pre-approve the ImmiIQ OAuth client for the whole firm if you prefer.
Configure
Pick which client records the mailbox routes to. Alt-email chips let a single client have several addresses. Set the default From identity so replies leave under the right agent even when the case is co-managed. Toggle the 90-day backfill or skip it.
Automate
Google Pub/Sub pushes new mail to ImmiIQ within seconds. Replies thread onto the client card. Compose inside the case and the send routes back through Gmail so it lands in your own Sent items. Nothing to babysit.
In the app
One-click connect. Zero DNS. Zero shared inbox.
The Gmail tile sits in the Integrations marketplace inside the app. Every user connects their own mailbox so nothing is co-mingled across the team.
Security posture
Sealed with your organisation's key. Never with ours.
Access and refresh tokens are sealed with AES-256-GCM using a per-organisation key derived from AUTH_SECRET via HKDF. Plaintext tokens never touch the database and never appear in logs. Every connect and disconnect is written to the tenant audit log with the actor, timestamp and IP. Mailboxes are scoped per user so one agent's Gmail never becomes shared infrastructure for the whole firm. Tenant isolation is enforced at the row level: Gmail data for one organisation cannot be queried, indexed or searched from another organisation under any code path. Revoking the connection tears down the Pub/Sub subscription, deletes the sealed row and stops all outbound routing through that account within seconds. Provider-sent messages still hit the org suppression list before send so a previously bounced address cannot be re-hit through a connected mailbox.
Frequently asked.
Is the Gmail integration two-way?
Yes. Every message a client sends to your connected Gmail address lands on the client timeline in ImmiIQ and every reply you compose inside ImmiIQ leaves from your own Gmail Sent folder with correct threading. Replies you type directly in Gmail also sync onto the case within about a minute so nothing gets lost between the two surfaces.
Which Google scopes does ImmiIQ ask for?
We request gmail.readonly for inbound sync, gmail.send for outbound sends and gmail.modify to add message labels for triage. We never request gmail.compose or the full Gmail scope. Google Workspace admins can review the exact scopes on the consent screen before allowing the connection and can restrict the OAuth client to specific users if they wish.
How quickly do inbound replies show up on the client timeline?
Within about a minute. The integration uses Google Pub/Sub push notifications so new mail is delivered to ImmiIQ within seconds of hitting your Gmail inbox. There is no polling delay and no need to keep a browser tab open.
Do Gmail-routed sends count against my ImmiIQ email quota?
No. Anything sent through your connected Gmail leaves via your own Google Workspace account and does not touch the ImmiIQ shared sending quota. Only the fallback path, used when no mailbox is connected on that agent, counts against the monthly limit.
How are Gmail OAuth tokens stored and what happens on disconnect?
Access and refresh tokens are sealed with AES-256-GCM using a per-organisation key derived from AUTH_SECRET via HKDF. Plaintext tokens never touch the database or logs. Disconnecting a mailbox tears down the Pub/Sub subscription and deletes the sealed row immediately. Every connect and disconnect is written to the tenant audit log.
Related integrations.
Connect Gmail in-app in under a minute.
Start a trial, connect your Google Workspace mailbox and see the last 90 days of client conversation on the timeline immediately.