The Gmail integration lets Emma send email on your behalf and read replies in the conversations she initiated. It’s used for personalized outreach drafted against your CRM lead lists and for general email sends from Emma. AgentWeb only reads replies to messages it sent. It does not read your inbox at large.Documentation Index
Fetch the complete documentation index at: https://docs.agentweb.pro/llms.txt
Use this file to discover all available pages before exploring further.
Connect
Sign in and authorize
Sign in with the Gmail account you want to use for outbound sends. Review the requested scopes and click Allow.
What Emma can do
| Capability | Behavior |
|---|---|
| Send | Send email through your connected Gmail address. Sends look like they came from you, not from AgentWeb. |
| Read replies | Read replies on conversations Emma initiated. Used to detect responses on outreach sequences. |
| Personalize at scale | Draft per-recipient emails using context from your CRM, Brand, and Knowledge Base. |
Disconnect
Click the Gmail card in Settings → Accounts and choose Disconnect. You can also revoke AgentWeb’s access from Google directly at myaccount.google.com/permissions.Troubleshooting
OAuth fails with 'access blocked'
OAuth fails with 'access blocked'
Some Google Workspace accounts restrict third-party app access at the admin level. Ask your Workspace admin to allow AgentWeb (
api.agentweb.pro) under Apps & integrations.Emails aren't sending
Emails aren't sending
Confirm the account is still connected — Settings → Accounts → Gmail card should say Connected. If it’s disconnected, reconnect. Google occasionally invalidates tokens after extended inactivity.
Replies aren't being detected
Replies aren't being detected
Replies are detected on conversations Emma initiated. If a recipient replies to a thread you started outside AgentWeb (not through Emma), it won’t show up. Forwarded threads and Reply-All to non-AgentWeb senders are also not tracked.