Skip to main content

Gmail Send Email Tool

Send emails via Gmail using either OAuth or App Password authentication.

Overview​

The Gmail Send Email tool allows you to send emails programmatically from your Gmail account. It supports both authentication methods:

  • OAuth: Full API access (recommended)
  • App Password: Simple SMTP sending

Prerequisites​

You must first connect a Gmail account:

Parameters​

ParameterTypeRequiredDescription
toarray[string]YesList of recipient email addresses
subjectstringYesEmail subject line
bodystringYesPlain text email body
html_bodystringNoHTML version of the email body
ccarray[string]NoList of CC recipients
bccarray[string]NoList of BCC recipients

Usage Examples​

Basic Email​

{
  "to": ["recipient@example.com"],
  "subject": "Hello from Reeva",
  "body": "This is a plain text email sent via Reeva!"
}

HTML Email​

{
  "to": ["recipient@example.com"],
  "subject": "Newsletter - January 2025",
  "body": "View this email in HTML for the best experience.",
  "html_body": "<h1>January Newsletter</h1><p>Check out our latest updates...</p>"
}

Email with CC and BCC​

{
  "to": ["primary@example.com"],
  "cc": ["teammate@company.com"],
  "bcc": ["archive@company.com"],
  "subject": "Project Update",
  "body": "Here's the latest status on our project..."
}

Multiple Recipients​

{
  "to": [
    "user1@example.com",
    "user2@example.com",
    "user3@example.com"
  ],
  "subject": "Team Announcement",
  "body": "Important update for the whole team..."
}

Response​

Success Response​

{
  "success": true,
  "message": "Email sent successfully to 1 recipient(s)",
  "from": "your-email@gmail.com",
  "to": ["recipient@example.com"],
  "subject": "Hello from Reeva"
}

Error Response​

{
  "error": "Gmail authentication failed. Check your credentials..."
}

Best Practices​

Email Formatting​

  • Always include both body and html_body for best compatibility
  • Plain text body acts as fallback for email clients that don't support HTML
  • Keep subject lines under 60 characters for mobile readability

Sending Limits​

Gmail has sending limits:

  • Individual accounts: 500 recipients per day
  • Google Workspace: 2,000 recipients per day

Authentication Method​

Choose based on your needs:

  • OAuth: Better for production apps, auto-refreshing tokens
  • App Password: Simpler setup, good for personal use

Common Use Cases​

1. Automated Notifications​

Send email alerts when specific events occur in your workflow.

2. Newsletter Distribution​

Send bulk emails to subscribers (respecting Gmail's sending limits).

3. Form Submissions​

Automatically email form responses to yourself or team members.

4. Report Distribution​

Email generated reports or summaries on a schedule.

5. Transactional Emails​

Send confirmations, receipts, or status updates to users.

Troubleshooting​

Authentication Errors​

"Gmail authentication failed"

  • Verify your Gmail account is still connected in Accounts
  • For OAuth: Token refresh may have failed - try reconnecting
  • For App Password: Check the password is still valid

Sending Errors​

"Failed to send email"

  • Check recipient email addresses are valid
  • Verify you haven't hit Gmail's sending limits
  • Ensure your account isn't restricted by Google

"Invalid credentials format"

  • Your account type doesn't match the tool's expectations
  • Reconnect your Gmail account

Credits Cost​

1 credit per email sent (regardless of number of recipients)

Support​

Need help? Check our troubleshooting guide or contact support.