---
title: 'GET /gmail/v1/users/{userId}/messages'
description: 'List messages in the mailbox'
---

# GET /gmail/v1/users/{userId}/messages

List messages in the mailbox

| Detail | Value |
|---|---|
| Operation ID | `listMessages` |
| Method | `GET` |
| Path | `/gmail/v1/users/{userId}/messages` |
| Connector | [Gmail](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `userId` | path | string | **Yes** |
| `q` | query | string | No |
| `maxResults` | query | integer | No |
| `pageToken` | query | string | No |

## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your Gmail connection from the Connection dropdown.
3. In the Operation dropdown, select `listMessages`.
4. Fill in the parameter fields that appear. Use `{{...}}` to reference upstream values.

**Required fields are marked — fill them or the call will fail at runtime.**

## What it returns

The `API Call` node writes the response to the workflow context:

```
{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}
```

Reference response fields downstream as <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Gmail API reference.