Skip to main content
GLAC Quote Tool sends quote emails through Zoho Mail using OAuth — your Zoho password is never stored or transmitted. Most email errors fall into one of two categories: the integration hasn’t been configured yet by your administrator, or your Zoho authorization token has expired or been revoked and needs to be renewed. Use the errors below to identify the cause and take the right corrective action.
This error means the Zoho integration has not been set up for your team. The administrator needs to add the Zoho OAuth app credentials (Client ID and Client Secret) to the server configuration and enable the Zoho Mail integration.Contact your administrator and ask them to complete the Zoho Mail integration setup. You will not be able to send emails through the tool until this is done.
This error occurs during the initial Zoho authorization step when the redirect URI used by the app does not exactly match the one registered in the Zoho Developer Console. Even a missing trailing slash can cause this failure.Your administrator needs to:
  1. Log in to the Zoho Developer Console.
  2. Open the GLAC Quote Tool OAuth app.
  3. Compare the Authorized Redirect URIs listed there against the actual URL of your deployed app (for example, https://quotes.globallinkconsulting.sg/).
  4. Update the URI in the Zoho console to match exactly, including any trailing slash.
Your Zoho refresh token has been revoked. This can happen if your Zoho organization administrator revokes app access, or if the token has been unused for an extended period.To resolve this, reconnect your Zoho account:
  1. Open the app and go to Settings in the sidebar.
  2. Click Disconnect Zoho Mail.
  3. Click Connect Zoho Mail and complete the authorization flow in the browser window that opens.
Once reconnected, the tool will obtain a fresh access token and resume sending emails on your behalf.
This error means the OAuth authorization was completed, but the app did not receive the permission it needs to read your Zoho Mail account details. The most likely cause is that the required scope (ZohoMail.messages.CREATE) was not granted during authorization.Reauthorize Zoho with the correct permissions:
  1. Go to Settings in the sidebar.
  2. Click Disconnect Zoho Mail.
  3. Click Connect Zoho Mail and carefully review the permissions screen — make sure you grant access to send mail on your behalf.
If you see an “Unauthorized” error or the send button appears to do nothing, you are likely in Demo Mode. Zoho Mail sending only works when the app is connected to Supabase (Supabase Mode), because the OAuth token exchange and email dispatch happen through a Supabase Edge Function.Check the mode indicator in the top-right corner. If it shows the orange ⚠️ Demo Mode badge, connect the app to Supabase first. See Connect GLAC Quote Tool to Supabase for steps.If you are already in Supabase Mode, try disconnecting and reconnecting Zoho from Settings.
If the send action completes without an error but the client reports not receiving the email, check the following in order:
  1. Verify the recipient address. Confirm the TO and CC fields in the email compose modal contain the correct email addresses before sending.
  2. Check your Zoho Sent folder. Log in to Zoho Mail and confirm the email appears in your Sent folder. If it does, the tool delivered the email successfully and the issue is on the delivery side.
  3. Ask the client to check their spam folder. First-time senders are sometimes filtered by spam rules, especially for business email domains.
If the email does not appear in your Zoho Sent folder, the send likely failed silently — reconnect Zoho from Settings and try again.
After reconnecting Zoho Mail, send a test email to yourself before sending to a client. This confirms the integration is working correctly and lets you verify the email content and formatting before it reaches the client.