Gmail

Node catalog Actions
On this page

Search, read and send Gmail messages, manage labels and trash.

Usage and specifics

Select a Gmail OAuth credential authorized for the operation. Use query and pagination to list messages; supply recipients and content to send. Check labels and permissions before modifying messages.

Technical type : gmail. 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 "" -
operation enum "list_messages" list_messages, get_message, send_message, modify_labels, trash_message, untrash_message, list_labels
messageId string "" -
query string "" -
pageSize number 100 -; ≥ 1, ≤ 500
pageToken string "" -
to string "" -
cc string "" -
bcc string "" -
subject string "" -
body string "" -
bodyType enum "text" text, html
addLabelIds string "" -
removeLabelIds string "" -

Configuration help

credentialId
Gmail credential
Use a Gmail OAuth credential. No password or service account. Permissions must allow the selected action.
operation
Action
Trash is reversible. To archive or mark as read, remove INBOX or UNREAD respectively.
bodyType
Message format
Plain text or HTML. MIME and Base64 URL encoding is automatic.
body
Body
Message content or expression. Maximum 5 MiB for the encoded MIME message.

Initial configuration

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

json
{
  "credentialId": "",
  "operation": "list_messages",
  "query": "",
  "pageSize": 100,
  "pageToken": "",
  "messageId": "",
  "to": "",
  "cc": "",
  "bcc": "",
  "subject": "",
  "body": "",
  "bodyType": "text",
  "addLabelIds": "",
  "removeLabelIds": ""
}

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.

See also : Expressions and data, Executions, Node catalog.