Gmail
Google integration · 4 node(s).
00Overview
Google Gmail email operations
Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.
01Connecting Gmail
Add your credentials as a Flomation environment secret, then pick them in each node. The connection fields are:
${secrets.your_secret}.02Draft
Gmail Draft
google/gmail/draft · Action
Manage Gmail drafts: create a new draft, list existing drafts, update a draft, or delete one. Use action='create' to compose without sending, 'list' to see drafts, 'update' to modify, 'delete' to remove.
| Field | Type | Details | |
|---|---|---|---|
| Action to perform | string | Required | choices: Create a new draft, List existing drafts, Update a draft, Delete a draft |
| Recipient (for create/update) | string | ||
| Subject (for create/update) | string | ||
| Body (for create/update) | text | ||
| Draft ID (for update/delete) | string | ||
| Account (email or label) | string | ||
| Google OAuth Credential (optional) | credential | ${credentials.GOOGLE_EMAIL} |
Returns: tool_result, draft_id, drafts, success, error
03Read
Gmail Read
google/gmail/read · Action
Search and read the USER's emails from their connected Gmail. When the user says 'my emails' or 'check my inbox', use this tool — it reads THEIR mailbox. Use Gmail search (e.g. 'is:unread newer_than:1d', 'from:someone') or email_id for a specific message.
| Field | Type | Details | |
|---|---|---|---|
| Gmail search query (e.g. 'from:boss@company.com', 'subject:urgent', 'is:unread') | string | is:unread | |
| Max emails to return (default 10, max 50) | integer | 10 | |
| Email ID to read in full (from a prior search) | string | ||
| Filter to a specific account email. Leave empty to search ALL user accounts. Never default to the agent's own email. | string | ||
| Google OAuth Credential (optional, overrides user tokens) | credential | ${credentials.GOOGLE_EMAIL} |
Returns: tool_result, emails, total_count, success, error
04Reply
Gmail Reply
google/gmail/reply · Action
Reply to an existing email. Requires the email_id from a previous email_read. Preserves the thread so the reply appears in the correct conversation.
| Field | Type | Details | |
|---|---|---|---|
| Email ID to reply to (from email_read) | string | Required | |
| Reply body (plain text) | text | Required | |
| Reply all (default false) | boolean | ||
| Sender display name (e.g. 'Ada Whitmore') | string | ||
| Account to send from (email or label) | string | ||
| Google OAuth Credential (optional, overrides user tokens) | credential | ${credentials.GOOGLE_EMAIL} |
Returns: tool_result, message_id, success, error
05Send
Gmail Send
google/gmail/send · Action
Send an email. Default sends from agent's account. Set account to user's email to send on their behalf.
| Field | Type | Details | |
|---|---|---|---|
| Recipient email address(es), comma-separated | string | Required | |
| Email subject | string | Required | |
| Email body / message content (plain text) | text | Required | |
| CC recipients (comma-separated) | string | ||
| BCC recipients (comma-separated) | string | ||
| Sender display name (e.g. 'Ada Whitmore', defaults to account label) | string | ||
| Sending account (email or label, empty for primary) | string | ||
| Google OAuth Credential (optional, overrides user tokens) | credential | ${credentials.GOOGLE_EMAIL} |
Returns: tool_result, message_id, thread_id, success, error
06Notes & Limitations
Behaviours and constraints worth knowing before you build with these nodes.
- Replying to a message requires the original email's ID from an earlier read step, so place a read node before any reply node to keep the response in the correct conversation thread.
- Searches use Gmail's native search syntax (for example is:unread, from:someone, newer_than:1d), the same operators as the Gmail search box, rather than plain keyword matching.
- Sending defaults to the connected account, so to send from the operator's own address you must explicitly set the account to their email.
- Very recently sent or received messages can take a short moment to surface in search results because Gmail indexes them asynchronously, so allow a brief delay before searching for a message you just handled.