> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentsdr.ai/llms.txt > Use this file to discover all available pages before exploring further. # Connect email > Connect Google Workspace, add the mailboxes campaigns send from, and set each mailbox's signature and sending hours. Email in AgentSDR sends and reads Gmail through a Google Workspace service account. You connect that account once for your organization, then add the individual mailboxes (for example `rep@yourcompany.com`) that campaigns send from. All of it lives under **Settings → Email**, which has three tabs: **Mailboxes**, **Connection** and **Sending rules**. Only Google Workspace mailboxes are supported today. Microsoft Outlook is listed on the **Connection** tab as "coming soon". ## Connect Google Workspace Open **Settings → Email → Connection**. The **Google Workspace** card shows **Connected** or **Not connected**, and what it powers: email accounts, campaigns and reply sync. The card opens a form with a **How to connect** guide. It lists the Google Cloud and Google Admin steps: enable the Gmail API, create a service account and a JSON key, then authorise the service account for the Gmail scopes in the Admin console (domain-wide delegation). The full walkthrough is in [Integrations](/integrations). Use **Upload key file** to fill the fields from the JSON key, or paste them by hand. * **Service account email** (required) * **Private key** (required) * **Gmail Pub/Sub topic** (optional) AgentSDR checks that Google accepts the key before it saves, so a typo fails on the form rather than on your first send. A topic that is filled in must look like `projects//topics/`. Without the **Gmail Pub/Sub topic**, sending works but replies are not picked up. Leave it empty only if you do not need reply detection, because reply detection is what stops a sequence when someone answers. Once connected, the card shows **Edit**, **Disconnect** and when the credentials were last verified. Disconnect pauses everything that depends on Google: email pages show a **Connect Google Workspace** prompt, background sending stops, and nothing is read from env variables as a fallback. Owners and admins manage this; see [Organizations](/workspace/organizations). ## Add a mailbox The credentials above let AgentSDR act for your domain. A mailbox is one address on that domain. Go to **Settings → Email → Mailboxes** and click **Add mailbox**. Until Google is connected this page shows the Connect prompt instead. The dialog is titled **Add a mailbox**. * **Email address** (required): a Google Workspace address covered by your domain-wide delegation. * **Display name** (optional): the name recipients see beside the address. * **Signature** (optional): added to every send from this mailbox. Click **Connect & test**. AgentSDR calls Gmail as that address. If it works you see **Mailbox connected**. If not, **The connection test failed** shows Google's reason and you can click **Try again**. An address can belong to only one organization. If it is already connected elsewhere, the dialog says so. ## Read the Mailboxes table Each row shows a status, how many emails went out today against the mailbox's daily limit, and its sending hours. | Status | Meaning | | - | - | | **Connected** | Can send. | | **Failed** | The last connection test failed. The error appears under the address; click **Test again**. | | **Connecting** | The first test has not finished. | | **Disabled** | Not sending. | Only **Connected** mailboxes send. The cards above the table summarise **Connected**, **Needs attention**, **Sent today** and **Left today** (daily limits of connected mailboxes minus what they sent). Failed mailboxes are sorted to the top. Use the **...** menu on a row for **Test connection**, **Send test email** (connected mailboxes only), **Sending hours**, **Signature** and **Remove mailbox**. Removing a mailbox stops it sending, and emails scheduled from it do not go out. ## Daily limit A new mailbox starts with the organization's **Emails per day, per mailbox** rule, which defaults to 30 (allowed 1 to 200). The table shows each mailbox's sent-today count against its own limit, and the queue never schedules more than that limit in a day. The page warns above about 50 a day from one Google Workspace mailbox, because deliverability usually drops and Google may throttle it. New mailboxes should start low. You change the default under [Sending rules](/workspace/sending-rules). The mailbox table does not currently have a control for editing one mailbox's limit. The limit is copied from the organization rule when the mailbox is added. ## Signature Choose **Signature** on a mailbox to edit it. It is plain text, such as a name and title. In a sequence, put `%signature%` where it should appear; if the email body has no placeholder, the signature is appended at the end. If the mailbox has no signature, the placeholder is removed rather than sent literally. ## Sending hours Choose **Sending hours** on a mailbox. Set a **Timezone**, then turn on the **Days** you want and a start and end time for each. The mailbox only sends inside this window, and emails due outside it wait for the next open slot. If every day is off, the mailbox will not send at all. A day whose end is before its start is treated as an overnight window. New mailboxes copy the organization's default: Monday to Friday, 09:00 to 18:00, in `Asia/Kolkata` unless you change it in [Sending rules](/workspace/sending-rules). Changing the default does not rewrite mailboxes that already exist. Between sends, each mailbox also waits a random gap, 18 to 24 minutes by default. Sending more often than every 10 minutes from one mailbox looks automated to spam filters. ## Related Build a sequence and send it from your mailboxes. Where replies arrive. Default limits, gaps and hours. The Google Cloud and Admin console steps. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.