The Email card connects your own mailbox, so that Send on a lead’s email draft sends from your address. PULSE has no shared sender and uses no email service provider. Connect one of:
| Option | How it connects | What PULSE may do |
|---|---|---|
| Gmail | Connect Gmail opens Google’s consent page (OAuth with PKCE). | Send mail (gmail.send), your address (openid email), and read your mail (gmail.readonly) so PULSE can see who answered. PULSE keeps only a short snippet of each reply to an email it sent, never the message. |
| Microsoft 365 | Connect Microsoft 365 opens Microsoft’s consent page. | Send mail as you (delegated Mail.Send), read your mail (Mail.Read) to see who answered, read your profile (User.Read), and stay connected (offline_access). |
| SMTP | Host, port (587 for STARTTLS, 465 for TLS), username, password and from address. | PULSE logs in before saving. A server that does not offer STARTTLS is refused: no password or message is sent unencrypted. |
Tokens and the SMTP password are sealed in the integrations table like every
other credential. Test asks the provider who the mailbox is and sends
nothing: Google’s token check (which must show gmail.send), Graph GET /me,
or an SMTP login. An expired Google or Microsoft token is refreshed once.
If several mailboxes are connected, PULSE sends from the most recently connected one that passed its check; the sheet names the address before you send.
What Send does
Leads → Email → Send sends the newest saved draft to the lead, records the
attempt (outreach_sends: lead, provider, provider message id, time, status)
and moves a new lead to contacted. Nothing is sent automatically. Send is
shown only when all of these hold; otherwise the sheet says which one is
missing and keeps Copy and Open in email:
- your account is an editor or admin;
- the administrator armed
PULSE_APPLY_ENABLEDand did not setPULSE_PUBLISH_EMAIL=false(see Switches); - a mailbox is connected and its last check passed;
- you are under the daily limit (
PULSE_EMAIL_DAILY_LIMIT, 50 by default).
Outreach from the sheet is one-to-one, so it carries no List-Unsubscribe
header. A marketing send through the API (marketing=true) adds one.
Replies
PULSE looks for answers to the emails it sent, every 15 minutes and each time you open Leads, for sends from the last 30 days. A reply is matched on the sent email’s own thread (Gmail) or conversation (Microsoft 365), so other mail is never matched. A lead who answered is marked replied and shows under To do today on Leads, with the first words of the answer and Answer, until you move it past Talking. Only a short snippet (200 characters) is kept, sealed like every credential.
- A Gmail or Microsoft 365 mailbox connected before reply tracking, or without the reading permission, is never read. The Email card and To do today say to Reconnect, which asks for the permission again.
- An SMTP mailbox has no inbox PULSE can read: replies are not tracked, and the page says so. (IMAP is not supported.)
For the administrator
Gmail and Microsoft 365 use the instance’s own OAuth clients, read from the instance configuration, never from a repository secret:
- Set
PULSE_PUBLIC_BASE_URL. The redirect URI is<PULSE_PUBLIC_BASE_URL>/oauth/mail/callback. - Gmail: in the Google Cloud project behind
GOOGLE_CLIENT_IDandGOOGLE_CLIENT_SECRET, enable the Gmail API, add the redirect URI to the web client, and add thegmail.sendandgmail.readonlyscopes to the consent screen (gmail.readonlyis a restricted scope: Google requires app verification beyond 100 users). - Microsoft 365: register an app in Microsoft Entra, add the redirect URI as a
Web platform, grant the delegated Graph permissions
Mail.Send,Mail.Read,User.Readandoffline_access, create a client secret, and setMICROSOFT_CLIENT_ID,MICROSOFT_CLIENT_SECRETand, for a single-tenant app,MICROSOFT_TENANT_ID(defaultcommon).
A connect link works once and for ten minutes.
SMTP needs nothing from the administrator: each person enters their own
server. Sending by any route still needs PULSE_APPLY_ENABLED=true and
PULSE_PUBLISH_EMAIL not set to false; PULSE_EMAIL_DAILY_LIMIT (50) caps
each person’s sends per 24 hours. See
Switches and arming order.