ModuleX
Integrations
Gmail logo

Gmail integration

Communication · 2 actions · OAuth or Bearer token auth

Google Gmail email service for sending, reading, and managing emails.

Put Gmail to workView Gmail integration docs
Overview

The ModuleX Gmail integration lets a ModuleX agent operate Gmail on your behalf — running send and list actions across messages and labels — directly from a plain-English request, using your organization's own Gmail credentials. No pre-built workflow is required: the agent picks the right Gmail action for the task.

Gmail is a communication platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Gmail action — or, when you want a repeatable process, the composer assembles a Gmail workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Gmail in plain English

Type what you want. A ModuleX agent picks the right Gmail action — or chains several — and runs it. No workflow to build.

  • Send a new email via Gmail
    resolves tosend_message
  • Show me the labels that match what I describe
    resolves tolist_labels
Use cases

What you can automate with Gmail

  • Send a message where it needs to gosend_message
  • Pull a list of labels for a reportlist_labels
At a glance

Gmail integration at a glance

VendorGmail
CategoryCommunication
Actions available2
AuthenticationOAuth or Bearer token
Uses your own credentialsYes
Works with the assistantYes
Works in the composerYes
Multi-step / tool-chainingYes
Technical referenceView docs
Integration version1.0.0
Last updatedJun 2026
Reference

All 2 Gmail actions

Messages1
send_message
Send a new email via Gmail
Labels1
list_labels
List all available Gmail labels

See full parameters and response schemas in the Gmail integration docs

Two ways

Two ways to use Gmail in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Gmail action and runs it — no workflow to build.
Compose a workflowNeed it to happen every time? Describe the process and the composer wires Gmail into a repeatable workflow you can run on a schedule, from chat, or as an API.
Security

Connecting Gmail

OAuthGmail uses OAuth. You connect your Gmail account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.
Bearer tokenGmail uses bearer-token authentication. You provide a Gmail access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Gmail.

Step-by-step setup in the Gmail docs

Related

Pairs well with Gmail

Agents often chain Gmail with these — connect them once and the agent can use all of them in a single task.

Zoom23 actionsAgentMail21 actionsMicrosoft Outlook20 actionsTelegram Bot17 actionsTwilio17 actionsMicrosoft Teams12 actions
FAQ

Gmail + ModuleX FAQ

A ModuleX agent can run any of Gmail's 2 actions — across messages and labels — from a plain-English request, using your organization's own Gmail credentials.
No. The agent selects the right Gmail action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.
Through OAuth — you connect your Gmail account once and ModuleX stores the token encrypted, scoped to your organization.
2, spanning messages and labels.
Gmail runs on your own credentials, so any Gmail usage is billed by Gmail directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Gmail to work in ModuleX.

Connect Gmail once with your own credentials and let your agent run all 2 actions on demand.

Put Gmail to workView technical docs
Last updated: Jun 2026Browse all 175 integrations →