Trash Message: 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
Message ID messageId	string	Required	Gmail message ID — the hex string Gmail assigns to each message. Find via List Messages. Not the RFC822 Message-Id header.

Sample request

{
  "messageId": "e.g. 18a1b2c3d4e5f6"
}

Returns

{
  "id": "msg123",
  "snippet": "Hi, I wanted to discuss...",
  "labelIds": [
    "TRASH"
  ],
  "threadId": "thread123"
}

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

FAQ

Questions about Trash Message.

What does the Trash Message action do in Gmail?

Moves an email message to the trash (recoverable for 30 days). The safer cleanup default vs. permanent delete.

What inputs does Trash Message require?

Required: Message ID. 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 Trash Message support batch operations?

Yes. Run Trash Message 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