---
title: Gmail
description: Send email from the Gmail account you connect.
source: https://www.edgaze.ai/docs/builder/nodes/integration-gmail
section: builder
---
# Gmail

> Send email from the Gmail account you connect.

**Audience: Workflow creators.**

## Overview

Send email from the Gmail account you connect.

Use this block when its responsibility is clear in the graph. Give it a name that describes the work it performs, then test it with representative input before publishing.

## Setting it up

You never see anyone's Gmail sign-in, and you do not need your own Gmail account to build with this step. People who run the workflow connect their own account and approve exactly what it may do before it starts.

### Actions

- **Send an email** - Sends an email from the connected Gmail account. Makes a change. Needs: To, Subject, Message. People running it are asked to allow: _Send email from your Gmail account_.

### Filling in the fields

Every field can be filled three ways: **type it** (a fixed value), **from a step** (a value an earlier step produced - pick it from a list, no paths to type), or **text + steps** (fixed text with values from earlier steps woven in). The panel shows what will be sent, using sample data, and tells you before you publish if a field is missing or points at a step that is no longer connected.

### Trying it

Test runs from the canvas use sample Gmail data. Nothing reaches a real account until someone runs the published workflow with their own connection.

## Working examples

These are complete starting points, not decorative diagrams. Every graph is also available in the main template library and is checked by the workflow compiler.

### 1. Follow-up email after a run

**You will build:** An email the person reviews goes out from their account.

Sending is all this can do. Nobody's inbox is ever read. A send that cannot be checked never retries blindly; the run fails instead of double-sending.

```docsgraph
block-integration-gmail-follow-up-email-after-a-run
```

[Open this template](/templates/block-integration-gmail-follow-up-email-after-a-run) and adapt the labels, prompts, or credentials to your own workflow.

### 2. Expense receipt to the bookkeeper

**You will build:** The receipt arrives in the right inbox, formatted.

One approved address per run keeps money-adjacent email deliberate. The approval screen names exactly this action before the run can start.

```docsgraph
block-integration-gmail-expense-receipt-to-the-bookkeeper
```

[Open this template](/templates/block-integration-gmail-expense-receipt-to-the-bookkeeper) and adapt the labels, prompts, or credentials to your own workflow.

### 3. Daily summary email

**You will build:** A summary lands in an inbox, on schedule.

Email still beats chat for the people who matter here. A paused or interrupted run can't send half an email twice.

```docsgraph
block-integration-gmail-daily-summary-email
```

[Open this template](/templates/block-integration-gmail-daily-summary-email) and adapt the labels, prompts, or credentials to your own workflow.

## Ports

- **Input: Input** (`in`): `any`, optional, multi_object.
- **Output: Success** (`success`): `object`, optional, single.
- **Output: Error** (`error`): `object`, optional, single.

## Inspector

- **Action panel:** choose what the step does, which account resource it acts on, and where each field's value comes from. See _Setting it up_ above.

## Behavior

- **Input requirement:** Choose an action. Fields can come from earlier steps or be typed in.
- **Execution:** Runs through the Edgaze Gateway, which talks to the provider on the runner's behalf.
- **Timeout:** 30000 ms by default (1000 to 120000 ms).

## Cost

Uses outbound HTTP transport and may contribute to the run's compute cost.

## Security

- The person running the workflow connects their own account and approves exactly what this step may do before the run starts. The workflow never holds their sign-in, and you never see it.
- Actions that make changes are listed separately on the approval screen, and the run is limited to the account resources the person chose.

## Retry

If a step is interrupted mid-change, Edgaze checks with the provider whether the change went through before ever trying again, so nothing is posted or created twice.

## Production checklist

- Test the happy path and one malformed or empty input.
- Keep credentials out of prompts and published graph configuration.
- Set a timeout and retry policy that matches the operation's side effects.
- Name the final result so a runner can tell what success looks like.