This document outlines the functionality and characteristics of the Gmail Reader node, which enables automated email processing from Gmail accounts.Documentation Index
Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt
Use this file to discover all available pages before exploring further.
Node Inputs
The Gmail Reader node accepts the following inputs:- Label: The Gmail label to read from (default: ‘INBOX’)
- Number of Emails: Maximum number of emails to process. Leave blank to read all emails.
Optional Settings
- Search Query: Optional Gmail search syntax to filter emails
- Mark as Read: Whether to mark processed emails as read (default: False)
- Ignore Read Status: If checked, this will include both unread and previously read emails in your search. By default, only unread emails are processed
- Read Full Thread: If checked, the full message chain will be read for each email thread (default: False)
Date Range Filtering
Filter emails by a specific time period, this option is available underShow More Options
- Use Dates?: Enable this toggle to filter emails by time period
-
Date Range: Choose from preset ranges for quick filtering:
- Last 24 Hours
- Last Week
- Last Month
- Last 3 Months
- Last 6 Months
-
Use Exact Dates?: Toggle this option to specify custom date ranges
- When enabled, you can set precise Start and End dates
- When disabled, the preset Date Range selection is used
- Start Date (UTC): The beginning of your custom date range (only available when Use Exact Dates is enabled)
- End Date (UTC): The end of your custom date range (only available when Use Exact Dates is enabled)
- Historical email analysis
- Periodic reporting
- Retrieving emails from specific events or timeframes
- Automating regular email processing batches
Note: When “Use Exact Dates?” is enabled, you can expose the Start Date and End Date parameters through “Configure Inputs” and connect them directly to the Datetime node for dynamic date ranges.
Node Output
The Gmail Reader node produces the following outputs (all in list format):- Email Bodies: Content of the email messages
- Attached File Names: Attached file object
Note that multiple attachments are separated by a comma, eg:PDF1, PDF2. You can use theSplit Textnode here to output a list with each file.
- Message ID: Unique ID of each individual email
- Thread ID: Unique ID of the entire conversation thread that can contain multiple emails
- Sender Addresses: Email addresses of senders
- Recipient Addresses: All recipients (including CC/BCC)
- Subjects: Email subject lines
- Dates: Date & timestamp of emails (in UTC)
- Sender Display Names: Names of the email sender
Understanding Attachment Handling
The “Attached File Names” output provides the actual file objects from email attachments. These files can be connected directly to file operation nodes like PDF Reader, CSV Reader, or File Reader for immediate processing.
Multiple Attachments per Email
When a single email contains multiple attachments, they are combined into one output separated by commas:Node Functionality
The Gmail Reader node provides automated access to Gmail inbox content and email data. Key features include:- Support for Gmail search syntax filtering
- Date-based email filtering
- Attachment handling
- Customizable email processing options
- Secure authentication with Gumloop
Trigger Functionality
This node can also function as a trigger to start your workflow when new emails arrive in Gmail. Learn more about triggers in our Workflow Triggers documentation.
How the Gmail trigger works
The Gmail trigger polls your mailbox every ~60 seconds using Gmail’s incremental history API and fires your workflow when:- A new email arrives in the configured label, or
- An existing email gains the configured label after delivery (e.g. via a Gmail filter or manual labeling).
- Multiple triggers, multiple labels — you can configure multiple Gmail triggers on the same account, each watching a different label. There is no per-account label limit.
- Read status is not a filter — the trigger fires whether or not you’ve opened the email in your Gmail UI between when it arrived and when the next poll runs.
- Latency — emails are detected within ~30 seconds median, ~60 seconds worst case.
- Cost — polls with no new email do minimal work (one Gmail API call) and don’t run your workflow.
Trigger parameters
When the node is configured as a trigger, only a subset of its parameters apply:- Label — the Gmail label to watch (use
Inboxfor the general inbox). - Mark as Read? — whether to mark each fired email as read after processing.
- Read as HTML? — read the body as HTML instead of plain text.
When To Use
The Gmail Reader node is particularly valuable in scenarios requiring automated email processing. Common use cases include:- Customer Support: Automatically process incoming support emails
- Data Extraction: Extract information from scheduled reports
- Email Monitoring: Track important communications
- Attachment Processing: Handle incoming file attachments
- Processing order confirmations
- Collecting daily reports
- Monitoring support tickets
- Archiving attachments
Example Workflows
1. Weekly Email Report Processing
2. Monthly Invoice Collection
3. Daily Support Email Categorization
Important Considerations:
- Requires Authentication with Gmail - Set up in the Credentials page
- Manual mode processes only unread emails by default. Toggle
Ignore Read StatusunderShow More Optionsto include read emails. Trigger mode fires on new emails regardless of read status — see “How the Gmail trigger works” above. - Output types change to single
stringif reading just one email - Date filtering in UTC timezone may not match your local time
