Saltar al contenido principal

Documentation Index

Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt

Use this file to discover all available pages before exploring further.

Gmail is the formal communication channel that complements the immediacy of WhatsApp or Slack. While other integrations solve real-time coordination, Gmail allows your flows to send follow-ups, confirmations, proposals, and formal escalations from the connected account. In Brain Studio, this integration connects your inbox so flows and agents can send, search, and organize emails directly from the conversation, without anyone opening Gmail separately.

​
What Gmail enables

When you connect Gmail, you can:
  • Close the sales loop from chat — send proposals, follow-ups, or confirmations by email after a WhatsApp or web chat conversation
  • Search and read existing emails to provide context before the agent replies: previous threads, attachments, or communication status
  • Organize inbox operations from the flow — create labels, label messages, archive, or move to trash based on business rules
  • Prepare drafts for human review before sending sensitive emails
  • Manage signatures and aliases to keep brand consistency in automated communications

​
Installation

​
Prerequisites

  1. A Google account with access to Gmail.

​
How to connect it

The most direct way is using Jelou Agent: describe what you need and the agent connects Gmail automatically inside the flow. If you prefer manual installation, follow these steps in Marketplace. The connection uses Google OAuth; you do not need to copy credentials.
1

Open Marketplace

In Brain Studio, open Marketplace from the side menu.
2

Search Gmail

Find Gmail in the catalog and click Connect.
3

Authorize access with Google

A secure Google authorization window will open. Sign in if needed and accept the requested permissions.
4

Confirm installation

Back in Brain Studio, complete the wizard until the integration appears as connected.
In Marketplace, Gmail should appear as connected. From Canvas you can add its node, and in AI Agent → Tools you can enable it.

​
Available tools

At a high level, actions are grouped as:
  • Query — search emails, list labels, threads, and aliases.
  • Create or modify — send email, create drafts and labels, add or remove labels, update signatures.
  • Flow operations — approve workflow and download attachments.
  • Delete — send messages to trash and archive emails.
This integration exposes 16 tools in Brain Studio; below is each tool with purpose, inputs, and example.
If parameter names in the tool form do not match this page, prioritize the labels shown in Brain Studio when configuring the node.

​
Features

Adds one or more labels to an existing message using the Gmail message modify API.Inputs:
  • messageId (string) — Message ID.
  • addLabelIds (array of string) — Label IDs to add (e.g. STARRED, IMPORTANT, or a custom label ID).
Example:
{
  "messageId": "188c9a0f12abcde3",
  "addLabelIds": ["Label_123", "STARRED"]
}
Google documentation: users.messages.modify
Suspends flow execution until approval is completed via the email approval mechanism configured in the platform. Use when a human must validate before the flow continues.Inputs:
  • Depends on your flow configuration (approval identifiers, message, recipients, etc.). Check the fields in Brain Studio.
Exact parameters are defined by your flow and the tool in the builder.
Documentation: suspend and resume flows
Archives a message (typically by removing the INBOX label or equivalent).Inputs:
  • messageId (string) — Message ID to archive.
Example:
{
  "messageId": "188c9a0f12abcde3"
}
Google documentation: users.messages.modify
Creates a message draft in the connected account.Inputs:
  • to (optional, array of string) — Recipients.
  • subject (optional, string) — Subject.
  • body / htmlBody (optional, string) — Plain text or HTML body.
  • threadId (optional, string) — To reply in an existing thread.
Example:
{
  "to": ["[email protected]"],
  "subject": "Proposal (draft)",
  "body": "Hi, here is the proposal for review."
}
Google documentation: users.drafts.create
Creates a new label in the Gmail account.Inputs:
  • name (string) — Visible label name.
  • messageListVisibility / labelListVisibility (optional, string) — Visibility per Gmail API.
Example:
{
  "name": "Client / Priority",
  "messageListVisibility": "show",
  "labelListVisibility": "labelShow"
}
Google documentation: users.labels.create
Moves the message to Trash (not necessarily permanent deletion unless the tool states otherwise).Inputs:
  • messageId (string) — Message ID.
Example:
{
  "messageId": "188c9a0f12abcde3"
}
Google documentation: users.messages.trash
Retrieves an attachment by attachmentId for a message (e.g. to save or process in the flow).Inputs:
  • messageId (string) — Message ID.
  • attachmentId (string) — Attachment ID returned by the API when listing or getting the message.
Example:
{
  "messageId": "188c9a0f12abcde3",
  "attachmentId": "ANGjdJ8..."
}
Google documentation: users.messages.attachments.get
Searches messages using Gmail search (same syntax as the Gmail search bar).Inputs:
  • query (string) — Query (e.g. from:[email protected] is:unread).
  • maxResults (optional, number) — Max results.
Example:
{
  "query": "from:[email protected] subject:Invoice is:unread",
  "maxResults": 20
}
Google documentation: users.messages.list
Gets the configuration for one “Send mail as” alias for the authenticated user.Inputs:
  • sendAsEmail (string) — Alias address (must exist in send-as settings).
Example:
{
  "sendAsEmail": "[email protected]"
}
Google documentation: users.settings.sendAs.get
Lists all labels in the account (system and custom).Inputs:
  • Usually none required.
Example:
{}
Google documentation: users.labels.list
Lists all “Send mail as” addresses configured for the user.Inputs:
  • Usually none required.
Example:
{}
Google documentation: users.settings.sendAs.list
Retrieves messages in a thread by threadId.Inputs:
  • threadId (string) — Thread ID.
Example:
{
  "threadId": "188c1234abcd5678"
}
Google documentation: users.threads.get
Removes one or more labels from a message.Inputs:
  • messageId (string) — Message ID.
  • removeLabelIds (array of string) — Label IDs to remove.
Example:
{
  "messageId": "188c9a0f12abcde3",
  "removeLabelIds": ["INBOX", "UNREAD"]
}
Google documentation: users.messages.modify
Sends email from the connected account, with HTML, CC, BCC, and replies in a thread.Inputs:
  • to (array of string) — Recipients.
  • subject (string) — Subject.
  • body (string) — Plain text body when not using HTML only.
  • htmlBody (optional, string) — HTML body.
  • mimeType (optional, enum) — text/plain | text/html | multipart/alternative.
  • cc / bcc (optional, array of string)
  • threadId / inReplyTo (optional, string) — For replies in a thread.
Example:
{
  "to": ["[email protected]"],
  "subject": "Project update",
  "body": "Hi, here is the summary.",
  "htmlBody": "<p>Hi,</p><p>Here is the <strong>summary</strong>.</p>",
  "cc": ["[email protected]"],
  "threadId": "188c1234abcd5678"
}
Google documentation: users.messages.send
Updates the signature for a specific address in an organization context. Often requires a Google Cloud service account with domain-wide delegation and admin permissions.Inputs:
  • sendAsEmail (string) — “Send mail as” address to update.
  • signature (string) — HTML or text signature content.
  • Other optional fields per API (replyToAddress, etc.).
This action is not available for every account. If it fails or is missing, confirm with your Google Workspace admin and Brain Studio support.
Example:
{
  "sendAsEmail": "[email protected]",
  "signature": "<p>Regards,<br/>Support team</p>"
}
Google documentation: users.settings.sendAs.update
Updates the signature for the user’s primary sending address.Inputs:
  • signature (string) — Signature content (HTML as allowed by the API).
  • Additional parameters if the form shows them (e.g. default send-as identifier).
Example:
{
  "signature": "<p>--<br/>First Last<br/>Tel: +1 555 000 0000</p>"
}
Google documentation: users.settings.sendAs.update

​
How to use in Brain

Once connected, you can use Gmail in two surfaces:

​
In AI Agent

Ideal when users want to search, draft, reply to, or label email in natural language.
1

Open the AI Agent node

In Canvas, select or add the AI Agent node.
2

Open Tools

In the right panel, open the Tools tab.
3

Add Gmail

Use Add tool, search for Gmail, and enable it.
4

Configure tools

Choose the full integration or enable only the actions you need. Adjust the prompt to request recipient, subject, and body if missing; use draft and confirmation before Send email on sensitive messages; and use search, labels, or archive when users ask to organize the inbox.
Gmail appears in the agent tools list and you can open its settings using the gear icon.
The agent will automatically decide when to search, draft, or send emails based on the conversation.

​
In Canvas

Ideal when you need full flow control (for example: validate recipient → draft → confirm → send).
1

Drag Gmail into Canvas

In the side panel, open Marketplace and drag Gmail into the flow.
2

Select the tool

With the node selected, in Tools choose the action (for example Send email).
3

Configure request body and memory

Fill in the request body JSON and, if needed, Save response to a memory variable.
4

Connect the flow

Link the Task completed and An error occurred outputs to the next nodes.
The node is ready to run in the order defined by your flow.
Configuration example: The node editor shows a JSON body aligned with the Send email tool. Fields depend on the selected tool; this example covers a basic send using recipient, subject, and body from memory. 
{
  "to": ["{{$memory.destination_email}}"],
  "subject": "{{$memory.subject}}",
  "body": "{{$memory.message}}",
  "cc": ["{{$memory.cc_email}}"]
}

​
Use cases

The prospect shows interest over WhatsApp. Instead of an executive opening Gmail afterward, the flow sends the proposal or follow-up from the connected account in the same process.Specific example: a B2B agency receives leads through web chat. The prospect asks for pricing information. The agent collects email and needs, drafts a follow-up email with the proposal, and sends it via Gmail. The lead receives follow-up without depending on manual drafting. If review is required, the flow creates a draft first for executive approval.Ideal for: B2B sales, agencies, and SaaS with conversational lead generation where follow-up speed matters.
When a support conversation must move to formal email (due to internal policy, customer type, or traceability), the flow builds the message with case context and sends it without copy-paste.Specific example: a financial services company closes a support case via WhatsApp. The flow builds an email to [email protected] with subject, case summary, applied resolution, and ticket reference. The email thread remains as formal process backup.Ideal for: customer support, help desks, compliance, and onboarding processes requiring formal communication and traceability.
An executive can ask on WhatsApp, “Do I have pending emails from Acme?” and the agent searches, summarizes, and even prepares a draft response.Specific example: an independent consultant with high email volume asks on WhatsApp while heading to a meeting: “What did the client reply about the budget?” The agent finds the thread by sender and subject, summarizes the latest response, and offers to draft an answer. The consultant approves and the email is sent without opening Gmail.Ideal for: professionals with high email volume, executives, and small teams operating from mobile.

​
Integrations that combine well with Gmail

After scheduling a meeting in Google Calendar, the flow can send a confirmation email with date, time, meeting link, and prep materials.Combined flow: event created in Google Calendar → email via Gmail to attendee with details and agenda.Google Calendar documentation
Each sent email can be logged in a spreadsheet as an operational log: recipient, subject, date, and status. Useful for sales follow-up or communication audits.Combined flow: email sent via Gmail → new row in Sheets with recipient, subject, and timestamp.Google Sheets documentation
The flow can update the HubSpot contact or deal and send follow-up email from Gmail in the same process, aligning CRM and formal communication.Combined flow: deal updated in HubSpot → proposal email to contact via Gmail.HubSpot documentation
When email needs an attachment that already exists in Drive (proposal, contract, report), the flow can find it, adjust permissions, and include the link in email without manual intervention.Combined flow: search file in Drive → generate shared link → send email with link via Gmail.Google Drive documentation

Integrations

Catalog of integrations available in Marketplace.

How to use integrations in Brain

General flow for installing and using integrations in Brain Studio.