Before you start
Ticks are kept in this browser only.
Follow the path that matches your account. Provider screenshots come from the linked official documentation and may show a different theme or older navigation. Configuration examples are labelled separately.
Permissions to choose
Use these exact permission names. Conditional permissions are needed only for the features described.
| Permission / scope | When needed | What it allows |
|---|---|---|
https://www.googleapis.com/auth/gmail.readonly | Required | Read message content, attachment data and the connected mailbox identity.A restricted Google scope. It grants mailbox read access; Revient only keeps messages that match a case. |
gmail.send / gmail.modify / gmail.compose / https://mail.google.com/ | Not requested | Revient does not need permission to send, change or delete Gmail messages. |
Automatic email evidence | Required | On as soon as the mailbox is connected. Exact case matches are kept and assessed automatically. Pause it under Integrations → Manage. |
Approve read access only. Revient requests offline access so it can refresh the connection; this is an OAuth setting, not a separate Gmail scope. Case correspondence remains workspace-scoped and is not used for general model training.
Connect your mailbox and add evidence
You do not need a Google Cloud project, client ID or client secret. Complete these steps once Revient's Google connection is available.
Start from Gmail in Integrations
Revient → Integrations → Gmail → Connect Gmail
- Open the Gmail connection drawer and click Continue to Google.
- If the button is unavailable and says operator setup is required, stop here until Revient configures its Google application. Creating a personal developer app is not a merchant onboarding step.
You should seeGoogle opens its account-selection and consent flow. You are not asked to paste your Gmail password or an API secret into Revient.Choose the account and approve read access
Google → account picker → app access request
- Select the authorised test mailbox. Sign in on Google's page if needed.
- Check the application identity and its requested Gmail read access. Continue only for the Revient application arranged for your test.
- Approve access and wait to return to Revient. If Google blocks access, follow the relevant failure guidance below instead of creating another connection repeatedly.
You should seeThe selected email address appears as CONNECTED in the Gmail drawer. This proves authorisation; the next steps verify that case correspondence can be found and retained.Open a case and check its email
Revient → Cases → selected case → Evidence
- Connecting a mailbox turns on automatic checks. Every active case is checked for messages that mention its order number and involve the customer. You do not search or pick messages yourself.
- Open a case and go to Evidence. Under Email you see each connected mailbox and when it was last checked. Click Recheck mailbox now to queue a fresh check for that case.
- If a check fails because access expired, the case shows the reason with a link to reconnect. Other failures retry automatically.
- Pause automatic checks under Integrations → Manage. Disconnecting stops future reads but keeps evidence already saved to cases.
You should seeMatching messages appear in the case's evidence list under Communication after the check finishes, with sender, date and the message text.Review the matched correspondence
Revient → case → Evidence → Communication
- Click a message in the evidence list to see its sender, recipients, date and body. Attachments are scanned privately before they are kept.
- Matched messages are kept and assessed automatically. Messages that mention the order but not the customer, or mix several orders, are not kept.
You should seeEvery matched message shows in Communication with its source and time.Disconnect or remove retained evidence when needed
Revient → Integrations → Gmail → Manage
- Choose Disconnect mailbox on the correct account to stop future Revient reads. Revient also attempts to revoke the Google grant.
- To confirm provider-side revocation, review Revient in your Google Account's third-party connections.
- After disconnecting, choose Remove account and confirm to clear it from Integrations. Selected case evidence stays. Use Remove email or Remove file on its case to remove stored content explicitly.
You should seeThe connection is DISCONNECTED. Existing selected evidence remains available until you explicitly remove it.
Revient operator: configure Google onceRevient operator setup. Customers do not need to register their own Revient app.
Revient operator: configure Google once
Only the team operating this Revient deployment completes this section. Merchant customers use the sign-in steps above.
Enable Gmail in the Revient Google project
Google Cloud Console → project picker → APIs & Services → Library
- Select the Google Cloud project owned by Revient, search for Gmail API, open it and click Enable.
- Keep this project selected for the consent and client setup that follows.
You should seeThe selected project's Gmail API is enabled.Set up the app identity and test audience
Google Auth platform → Branding, then Audience
- Use Get Started if this project has no auth configuration. Enter the Revient app identity, support contact and developer contact, then complete the displayed setup.
- For testing merchant accounts outside Revient's Workspace organisation, select External and keep the publishing status Testing.
- In Audience → Test users → Add users, enter each authorised test mailbox and save. Use Internal only for an actual organisation-internal app.
You should seeThe intended mailbox is in the test-user list for this OAuth project.Add only the Gmail read scope
Google Auth platform → Data Access → Add or Remove Scopes
- Find or manually enter https://www.googleapis.com/auth/gmail.readonly, apply the selection and save.
- Do not add sending or mailbox-write scopes. Production availability requires the applicable restricted-scope verification and security review; a working test grant is not that approval.
You should seeThe scope list includes gmail.readonly. Production review remains a separate operator task.Create the server Web client and callback
Google Auth platform → Clients → Create Client
- Choose Web application and give this deployment a recognisable client name.
- Under Authorised redirect URIs, add the complete callback shown below, then create the client. The path, HTTPS origin and trailing slash must match Revient's configuration.
- Save the generated client ID and secret directly into the operator's secure deployment configuration. Do not put them into chat, screenshots, tickets or source control.
You should seeA Web OAuth client exists with the correct callback. Merchants will never need these application credentials.Configure Revient and verify a matched message
Railway → Revient service → Variables, then Revient → Integrations
- Configure GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and GOOGLE_REDIRECT_URI for the service handling the connection. Redeploy with the existing evidence-testing settings preserved.
- Use the merchant flow with an authorised test account, then search a test case, retain one known message and verify its optional attachment. Do not mark Gmail live-verified from the connection badge alone.
- Plan for reconnects: Google's external Testing grants with Gmail access expire after seven days. Production review and deployment readiness must be completed separately.
You should seeThe Gmail connection button is available, Google returns to the callback, and a test case shows its matched message under Evidence → Communication.
Review selected correspondence
Check the source facts and processing result after completing the provider-specific connection steps.
Check the matched email on a case
Revient → selected Case → Evidence
- Automatic checks run on every active case once the mailbox is connected. Messages that mention the order number and involve the customer are kept and assessed; nothing else is kept.
- Open Evidence → Communication on a case to read each matched message. Use Recheck mailbox now under Email to queue a fresh check.
- Revient AI stays unavailable if its approved provider configuration is missing. Deterministic checks and existing evidence remain available.
- Gmail-derived material is excluded from shared learning. Pause automatic checks under Integrations → Manage; disconnect stops future reads without deleting retained case history.
You should seeMatched correspondence appears on the case automatically. No customer messages are sent by Revient.
Match these fields in Revient
Enter your own account’s values. Example values are for orientation; do not paste them as credentials.
| Revient field | Where to find it | Example / guidance |
|---|---|---|
| Google account | Choose the mailbox in Google's account picker after Continue to Google. | Your authorised Gmail or Google Workspace account |
| Connected mailbox | Case → Evidence → Email shows each connected mailbox and when it was last checked. | The mailbox containing this order's correspondence |
Callback address for the Revient operatorOnly the operator configures this address in the provider application.
Register the complete address, including the path:https://www.revient.io/api/integrations/gmail/callback
If something goes wrong
Continue to Google is disabled
Revient's Google application settings are missing or invalid. The operator must complete the setup section; merchants do not need to create their own client.
Google blocks this test account
Confirm the exact signed-in address is on the same project's Audience → Test users list. A Workspace administrator may also need to allow the application under the organisation's policy.
redirect_uri_mismatch
The operator must match the full registered callback to GOOGLE_REDIRECT_URI, including HTTPS, host, path and trailing slash. Start a fresh connection after correcting it.
Connection worked, then needs attention
Reconnect through Continue to Google. External Testing grants expire after seven days; revocation, password changes or administrator policy can also invalidate Gmail refresh access.
No messages, expired selection or unavailable attachment
Check the case's saved identifiers and displayed date window. Search again for an expired selection. For files, check the supported type, 10 MB limit, five-file limit and scanner readiness.
Common questions
Does Gmail supply payment or delivery evidence?
No. Gmail supplies correspondence you choose to keep on a case. Payment authorisation, refunds, returns and tracking come from the store and the carrier.
Does every merchant need a Google Cloud project?
No. Revient configures its Google app once. You sign in and approve access; test users must be admitted to its testing audience until applicable production requirements are completed.
Does Google restrict the grant to one case?
No. gmail.readonly is a mailbox-level read permission. Revient limits checks to active case identifiers and retains exact matches only when the workspace automatic-evidence authorization is enabled; ambiguous messages stay in review.
Why are staff and AI permissions separate?
Authorising Google allows the connector to retrieve case candidates. Revient separately records which retained messages you allow staff to read or AI to assess. Neither permission enables sending mail.
Will disconnect erase saved email evidence?
No. It stops new reads; case evidence is retained until you remove it from its case. Revoking a message-use permission also does not erase its stored content or earlier assessment history.
What is the difference between Refresh evidence and Recheck stored evidence?
Refresh evidence queues new reads from available connected sources and already selected mailbox messages, then tracking and reassessment. Recheck stored evidence reassesses the retained facts without claiming a new provider read. Existing findings stay visible until the work finishes; unavailable sources and partial refusals are reported for each case.
Which disputes receive recovery scoring?
Shopify intake accepts only CHARGEBACK disputes with final status LOST and a verified remaining disputed balance. Inquiries, won and open outcomes are excluded before customer enrichment, tracking, scoring and AI. Historical non-qualifying records remain in internal audit history, outside merchant intake and active Cases. An order or tracking number alone does not establish a lost dispute. Supply the actual confirmed loss and preserve its original order and dispute identities.
Will testing send messages or release a case?
Evidence-testing mode blocks customer, agency and buyer delivery. Importing records or reviewing an assessment does not release a case.
What happens when I disconnect?
New reads stop and the Revient connection is disabled. Evidence already retained remains subject to the workspace retention and removal controls. Revoke the application or key in the provider account as well if you want to remove its access there.
Source documentation
Use these provider pages if a menu name has moved or your plan shows different options.