Short answer: Drop the "Gmail → List Messages" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Search Query q | string | Optional | Gmail search query (same syntax as the Gmail search box) |
Max Results maxResults | string | Optional | Max messages to return (hard cap: 20) |
Label labelIds | string | Optional | Comma-separated Gmail label IDs. Find via List Labels. |
{"q": "e.g. from:john@example.com is:unread after:2025/01/01","maxResults": "10","labelIds": "e.g. INBOX, UNREAD, STARRED"}
{"messages": [{"id": "msg123","payload": {"body": {"data": "base64..."},"headers": [{"name": "Subject","value": "Project update"},{"name": "From","value": "alice@example.com"}]},"snippet": "Hi, I wanted to discuss...","labelIds": ["INBOX","UNREAD"],"threadId": "thread123"}],"resultSizeEstimate": 42}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.