Skip to main content
Node type: gmail_new_email_trigger · Version: 1 · Category: Triggers Poll Gmail safely for matching messages. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Start triage, drafting, or notification flows from matching Gmail messages.
  • Filter at the trigger when only a sender, recipient, subject fragment, label, or attachment state is relevant.

​
Example: Draft replies to support mail

Poll a connected support inbox every five minutes for messages whose subject contains Support.
Example settings
This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector.
  1. Select the Gmail connection and add the narrowest useful filters.
  2. Map fields from the email output into analysis or draft nodes.
  3. Prefer Create Gmail Draft until the recipient logic has been reviewed.

​
Configuration

Message IDs are persisted per workflow to prevent the same email from starting repeated runs.

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • sndbox persists observed message IDs per workflow so the same message does not repeatedly trigger it.
  • Plain text is included by default; enabling HTML increases the amount and sensitivity of data stored in execution evidence.
  • The editor catalogue declares email (object) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • A poll interval is not an exact delivery SLA; the next poll must run and the event must enter the queue.
  • If no messages match, test each filter independently and confirm the connection can still access the mailbox.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.