Why send from your own account
When GetSalesClaw sends emails through your Gmail (or any SMTP provider), the emails come from your own domain with your own authentication records. This matters for three reasons:
- Deliverability: Emails sent from your authenticated domain with proper SPF and DKIM records land in the inbox, not the spam folder. Your domain reputation stays intact because GetSalesClaw throttles sending volume automatically.
- Trust: Prospects see your real email address and domain. There is no third-party sending domain to raise suspicion. When someone hits reply, it goes straight to your inbox.
- Compliance: Every email includes an automatic unsubscribe link. You send from your own domain, so you are fully in control of your sending practices and GDPR/CAN-SPAM obligations.
How to set up Gmail SMTP
Connecting Gmail takes about 5 minutes. You need to create an App Password, which lets GetSalesClaw send emails through your Gmail account without sharing your main password.
Enable 2-Factor Authentication
Go to myaccount.google.com → Security → 2-Step Verification and enable it. This is required by Google before you can create an App Password.
Create an App Password
Go to myaccount.google.com → Security → App passwords. Select "Mail" as the app and "Other" as the device (name it "GetSalesClaw"). Google generates a 16-character password. Copy it immediately -- you will not see it again.
Enter SMTP settings in GetSalesClaw
During onboarding (or in your dashboard under Settings), select "SMTP" as your email method and enter the following settings:
| Setting | Value |
|---|---|
| SMTP Host | smtp.gmail.com |
| SMTP Port | 587 |
| SMTP User | your-email@gmail.com (or your Google Workspace email) |
| SMTP Password | The 16-character App Password from step 2 |
GetSalesClaw encrypts your SMTP credentials and stores them in an isolated, permission-restricted file on EU-hosted servers. Your password is never exposed in logs, dashboards, or API responses.
SPF, DKIM, and DMARC
If you send from a Gmail address (@gmail.com), Google handles SPF and DKIM automatically. Your emails are signed and authenticated out of the box.
If you use Google Workspace with a custom domain (e.g., you@yourcompany.com), make sure your DNS records include:
- SPF: A TXT record on your domain that includes
include:_spf.google.com. - DKIM: Generate a DKIM key in Google Workspace Admin → Apps → Gmail → Authenticate email, then add the TXT record to your DNS.
- DMARC: Add a TXT record like
v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.comto start monitoring. Upgrade top=quarantineorp=rejectonce you confirm everything passes.
Proper authentication is the single biggest factor in email deliverability. GetSalesClaw cannot fix DNS issues for you, but the setup takes 10 minutes and protects every email you send -- not just the ones from GetSalesClaw.
Also works with any SMTP provider
GetSalesClaw is not limited to Gmail. Any SMTP server works. Here are common configurations:
| Provider | Host | Port |
|---|---|---|
| Gmail / Google Workspace | smtp.gmail.com | 587 |
| Outlook / Microsoft 365 | smtp.office365.com | 587 |
| OVH | ssl0.ovh.net | 587 |
| Zoho Mail | smtp.zoho.com | 587 |
| Amazon SES | email-smtp.us-east-1.amazonaws.com | 587 |
Just enter the host, port, username, and password during setup. GetSalesClaw handles TLS negotiation and connection pooling automatically.
Sending limits and throttling
Gmail allows up to 500 emails per day on free accounts and 2,000 per day on Google Workspace. GetSalesClaw respects these limits and spaces out sending throughout the day to protect your domain reputation.
Tip: For higher sending volumes (500+ emails/day), consider using Resend or Amazon SES instead of Gmail SMTP. These services are designed for transactional and marketing email at scale with built-in deliverability analytics.
GetSalesClaw also adds a random delay between emails (30-120 seconds) to mimic natural human sending patterns. This reduces the risk of triggering spam filters or rate limits from your email provider.