Skip to main content

Emails Not Being Sent

Problem

You have email delivery configured on your automation, but emails are not being sent after document generation.

Causes & Solutions

Verify that email sending is turned on in your automation’s output settings. Go to your automation page and check the Send Email section under output options.

Gmail Sender Setup

Problem

You want to send emails from your own Gmail address instead of the default DocsAutomator sender, but emails are still coming from DocsAutomator.

Solution

1

Connect Google account

Go to Settings > Integrations and ensure your Google account is connected with Gmail permissions.
2

Configure email sender

In your automation’s email output settings, select Gmail as the sender instead of the default DocsAutomator option.
3

Select Gmail account

Choose which connected Gmail account to send from. If you have multiple Google accounts connected, select the appropriate one.
4

Set sender name (optional)

You can customize the “From” name that recipients see. If left blank, your Gmail account name will be used.
Using Gmail as the sender means emails come from your own email address, which can improve deliverability and allow recipients to reply directly to you.

Attachment Issues

Problem

The generated PDF is not attached to the email, or the attachment fails.

Common Causes

  • PDF generation failed: If the PDF could not be generated, there is nothing to attach. Check Run History for errors.
  • File too large: Very large PDFs (with many high-resolution images) may exceed email attachment limits. Optimize images in your template.
  • Airtable attachment URLs: If you’re forwarding Airtable attachment URLs in emails, these temporary URLs may have expired by the time the email is sent. See the Airtable Attachment URL Issue guide.

Test Email Rate Limit

Problem

You receive an error when trying to send a test email, with a message indicating you’ve exceeded the rate limit.

Details

Test emails are rate-limited to 25 per hour per automation. This limit applies to the POST /sendTestEmail endpoint and the “Send Test Email” button in the app.

Solution

  • Wait for the rate limit window to reset (1 hour from your first test email)
  • Use the document preview feature to verify your template before sending test emails
  • Test with actual document generation on a single record instead of the test email function
The 25-per-hour limit is per automation. Each automation has its own separate quota.

Emails Going to Spam

Problem

Emails sent by DocsAutomator are landing in recipients’ spam folders.

Solutions

  • Use Gmail sender: Emails from your own Gmail address are less likely to be flagged as spam than emails from the default DocsAutomator sender
  • Avoid spam trigger words: Review your email subject and body for common spam trigger words
  • Ask recipients to whitelist: Have recipients add the sender address to their contacts or safe sender list
  • Check email content: Excessively large attachments, many links, or all-caps subject lines can trigger spam filters

Email Customization

Available Options

DocsAutomator supports customizing the following email fields:
FieldDescription
SubjectEmail subject line (supports placeholders)
BodyEmail body content (supports placeholders)
SenderDocsAutomator default or your Gmail account
Sender nameCustom “From” name (Gmail only)
Button colorCTA button color in the email template
You can use placeholders in both the email subject and body. For example, use {{customer_name}} in the subject line to personalize each email.

Send Email

Complete email configuration guide

Run History

Monitor email delivery status
Last modified on February 10, 2026