Send Email: Gmail action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
To to	email	Required	Recipient email (comma-separated for multiple)
Subject subject	string	Required	Email subject line.
Body body	html	Required	Email body in HTML format
CC cc	string	Optional	CC. e.g. "cc@example.com"
BCC bcc	string	Optional	BCC. e.g. "bcc@example.com"

Sample request

{
  "to": "recipient@example.com",
  "subject": "e.g. Meeting follow-up",
  "body": "<p>Hi John, thanks for the meeting today.</p>",
  "cc": "cc@example.com",
  "bcc": "bcc@example.com"
}

Returns

{
  "id": "msg123abc",
  "labelIds": [
    "SENT"
  ],
  "threadId": "thread123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Send Email.

What does the Send Email action do in Gmail?

Sends an email from your Gmail account with to, cc, bcc, subject, body (text or HTML), and attachments. The bread-and-butter outbound mail action.

What inputs does Send Email require?

Required: To, Subject, Body. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Gmail returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send Email support batch operations?

Yes. Run Send Email inside a Loop node to process arrays. Tiny Command handles Gmail's rate limits automatically so you don't have to throttle manually.

More actions