dataspaceGENE-GMailReader nameGENE-GMailReader skuGENE-GMAILREADER userAdrianus Warmenhoven version1.0.0

GENE-GMAIL

Name: GENE-GMAIL
Brand: Feluda.ai
SKU: GENE-GMAILREADER
Price: 1000 CREDITS
Availability: InStock

Give Your AI Secure, Searchable Gmail Access

1000 credits

SKU: GENE-GMAILREADER

Created: 2026-03-20 13:00:11.098837 +0000 UTC

Feluda Gmail Reader: Give Your AI Secure, Searchable Gmail Access

Feluda Gmail Reader connects your AI assistant and Feluda Flows to Gmail so it can read inbox data, fetch message details, manage labels, inspect attachments, and optionally send or reply to emails when explicitly enabled. It is built for practical daily workflows: triaging inboxes, finding key threads, extracting attachments, preparing summaries, and automating repetitive mailbox actions while keeping the user in control.

What value does Gmail Reader bring?

Gmail Reader turns mailbox operations into structured AI actions. Instead of asking users to manually search, copy, and interpret messages, the gene lets your AI retrieve exactly what is needed with clear commands. That means faster email research, better response drafting, cleaner task extraction, and less context switching in day-to-day work.

Faster inbox triage: Search and list messages with paging and filtering so your AI can prioritize what matters first.

Better context retrieval: Read full messages and threads to give your AI the full conversation history before it suggests actions.

Attachment awareness: Detect and read attachment content to support document-heavy workflows.

Optional send control: Keep outbound actions disabled by default and only allow sending when your team is ready.

Multi-account support: Work with account selection so the right mailbox is used for the right task.

Built-in help is always available

Every operation can be discovered with the tool's own help behavior, so an LLM can ask for guidance before taking action. This is important for reliability: your AI can self-check available commands, expected parameters, and command intent before it executes a mailbox task.

What operations does Gmail Reader support?

Gmail Reader exposes a unified command-based interface. The command parameter chooses the operation, while optional parameters narrow the result. This keeps usage consistent for both humans and LLM agents.

Command	What it does
listMessages	Search and list Gmail messages with support for paging, refresh behavior, and query-based retrieval.
readMessage	Fetch one or more messages by ID in full or alternate formats, including optional decode behavior.
getThread	Read an entire thread to preserve conversation context and chronology.
getContext	Return mailbox context information for orientation and workflow decisions.
getUnreadCount	Provide unread counts so the AI can prioritize mailbox actions.
listLabels	List label names and IDs for guided categorization workflows.
addLabel	Apply one or more labels to a message.
removeLabel	Remove one or more labels from a message.
markRead	Mark a message as read.
markUnread	Mark a message as unread.
archive	Archive a message from inbox-focused views.
saveAttachments	Save attachments from a specific message for downstream processing.
readAttachments	Read and convert attachment content for AI analysis.
getAttachmentSummary	Return a compact overview of attachment names, types, and sizes.
hasInvite	Detect calendar invite signals in a message to support scheduling workflows.
searchContacts	Search Google contacts cache by name or email when contacts integration is enabled.
syncContacts	Refresh contact cache from Google People API for accurate recipient resolution.
sendMessage	Send a new email when outbound sending is enabled in settings.
replyMessage	Send a threaded reply when outbound sending is enabled in settings.
logout	Clear the OAuth session so next live API action prompts sign-in again.
deleteAccount	Remove an authenticated account plus related cached mailbox data.

How to set up Gmail Reader — step by step

Getting started requires creating a Google Cloud OAuth app and saving your credentials in Feluda. Gmail Reader also returns setup guidance in authentication error messages, so your AI can guide users if credentials or scopes are missing. The summary below covers the key stages.

Step 1 — Create or select a Google Cloud project

Go to https://console.cloud.google.com/ and sign in with your Google account.

Create a new project or select an existing project.

Open APIs and Services and enable the Gmail API.

If you plan to use contact search/sync, also enable the Google People API.

Step 2 — Create an OAuth 2.0 Client ID

Open APIs and Services > Credentials.

Configure the OAuth consent screen if prompted (External or Internal based on your environment).

Create OAuth client ID with application type Desktop Application.

Use OAuth 2.0 PKCE user consent. This gene uses a local loopback callback with a randomized port at runtime (for example http://127.0.0.1:<random-port>/callback).

For Google OAuth, loopback redirect handling supports randomized localhost ports during PKCE sign-in.

Add scopes: openid, email, https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/gmail.send, https://www.googleapis.com/auth/gmail.modify, and optionally https://www.googleapis.com/auth/contacts.readonly when contacts integration is enabled.

Step 3 — Save your credentials in the Feluda Secrets page

Open the Feluda Desktop App and navigate to the Feluda Secrets page. Add the following secrets:

GmailClientID — the OAuth 2.0 Client ID from Google Cloud.

GmailClientSecret — the OAuth 2.0 Client Secret from Google Cloud.

DbEncryptionPassword — a strong password used to encrypt cached mailbox data at rest.

Step 4 — Configure gene settings

Open the Feluda Settings page for Gmail Reader and fill in the following:

Setting	Required	Description
`allowSendEmail`	Optional	Set to true only when you want to allow `sendMessage` and `replyMessage`. Disabled by default for safety.
`enableContacts`	Optional	Enable Google Contacts integration for `searchContacts` and `syncContacts`. Requires contacts scope approval.
`defaultMaxResults`	Optional	Default message count for list operations when maxResults is not provided.
`defaultFormat`	Optional	Default message format for read operations (`full`, `metadata`, `minimal`, `raw`).
`cacheRetentionDays`	Optional	How long cached messages are retained before pruning.
`maxCacheSizeMB`	Optional	Maximum cache database size before automatic compaction.
`snippetMaxChars`	Optional	Controls snippet truncation in list results.

Step 5 — Authorize and validate access

Run a read command such as getContext or listMessages from your AI.

Complete OAuth consent in the browser when prompted.

Confirm the gene can read messages, then optionally enable send operations if needed.

Operational safety and control

Gmail Reader is designed for safe adoption. Read operations are broadly available, while send operations can remain disabled until governance and review expectations are clear.

Send off by default: Outbound email commands are controlled by settings so teams can roll out safely.

Explicit account targeting: Account parameter support helps avoid accidental cross-account actions.

Session clarity: Logout and account deletion commands support controlled credential lifecycle management.

Cache-first resilience: Work can continue on cached data during disconnected or signed-out states for many read scenarios.

How Gmail Reader works in Feluda Flows

Gmail Reader becomes most powerful in Feluda Flows where reading, summarizing, classifying, and acting can be chained into reliable business workflows.

Inbox triage flow: Pull unread messages, classify urgency, apply labels, and generate a summary for daily review.

Attachment processing flow: Detect attachments, read content, extract tasks or facts, and route outcomes to downstream steps.

Customer reply flow: Read thread context, draft suggested replies, require approval, and optionally send.

Meeting preparation flow: Scan recent threads from specific participants, surface action items, and build a pre-meeting brief.

Compliance archive flow: Search targeted query windows, capture message metadata, and produce structured audit outputs.

What Gmail Reader does not do

Setting clear expectations helps users plan better automations.

No autonomous send without enablement: It will not send mail unless send permission is explicitly enabled.

No hidden credential sharing: OAuth credentials remain in user-controlled Feluda secrets and authorized user context.

No one-command business logic replacement: It provides strong mailbox primitives, while full workflows are built in Feluda Flows.

Who should use Gmail Reader?

Operations teams: For inbox triage, escalation handling, and routine process automation.

Founders and executives: For fast summaries, follow-up detection, and priority management across busy mailboxes.

Support and success teams: For thread-aware responses and consistent mailbox labeling standards.

Analysts and coordinators: For extracting structured insights from large volumes of email conversations.

Frequently asked questions

Can I read mail without being currently logged in? In many cases, yes, from local cache. Live API reads require OAuth authentication.

Can I control which account is used? Yes. Use account-aware command inputs to target the intended mailbox.

Can I fully sign out? Yes. Use logout to clear OAuth session state and require sign-in for next live API action.

How do I remove account data? Use deleteAccount to remove account-linked cached data.

Why choose Feluda Gmail Reader?

Feluda Gmail Reader gives your AI a practical, production-ready email capability set: rich read/search controls, attachment intelligence, workflow-safe write controls, and clear account/session management. If your organization depends on email operations, this gene helps convert inbox work into repeatable, automatable outcomes inside Feluda.