Create Message
gmail.create_message
ActionEmailconnection required
Calls gmail v1 POST /gmail/v1/users/{userId}/messages.
Directly inserts a message into only this user's mailbox similar to `IMAP APPEND`, bypassing most scanning and classification.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Gmail
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- token_uri
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
user User name or id. | string | Yes | — | — | — |
body The Message resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
classificationLabelValues | array | — |
historyId | string | — |
id | string | — |
internalDate | string | — |
labelIds | array | — |
payload | object | — |
raw | string | — |
sizeEstimate | integer | — |
snippet | string | — |
threadId | string | — |
{
"classificationLabelValues": [],
"historyId": "",
"id": "",
"internalDate": "",
"labelIds": [],
"payload": {},
"raw": "",
"sizeEstimate": 0,
"snippet": "",
"threadId": ""
}Templates that use Gmail
Solutions with Gmail
See Create Message run in a workflow.
In a technical demo we add the Gmail connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.