Gmail trigger

Node catalog Triggers

On this page

Start the workflow when a new Gmail message arrives.

Usage and specifics

Select Gmail OAuth, label and interval, then publish. The first poll initializes monitoring; new messages trigger subsequent runs. A simulated test does not validate OAuth or delivery.

Technical type : gmail_trigger. Runtime : nodulz.

Credentials and prerequisites

Gmail (integration / gmail). Google OAuth access to your Gmail mailbox with automatic token renewal.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`labelId`	`string`	`"INBOX"`	-
`pollInterval`	`number`	`60`	-; ≥ 30, ≤ 86400

Configuration help

credentialId Gmail credential: Use a Gmail OAuth credential. No password or service account. Permissions must allow the selected action.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "labelId": "INBOX",
  "pollInterval": 60
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.