Gmail n8n integrationAutomate Gmail with n8n.

Puts one or more existing labels on a single message, which is the filing a human would have done by dragging it.

• Message ID: the Gmail identifier of the message, in the shape of 172ce2c4a72cc243, usually carried over from the previous node with an expression, the {{ $json.id }} syntax that picks a field off the incoming item.
• Label Names or IDs: pick the labels in the dropdown, which loads from the credential, or specify their IDs with an expression.

Erases a message immediately and permanently. Gmail does not move it to the trash, and no later operation brings it back.

• Message ID: the identifier of the message to remove. Run a Get with that ID first if there is any doubt it exists, because a wrong one ends the execution on Bad request - please check your parameters.

Reads a single message back into the workflow, with its headers and, on demand, its attachments.

• Message ID: the message to retrieve.
• Simplify: on, the node returns message IDs, labels and the From, To, CC, BCC and Subject headers; off, the full raw payload.
• Download Attachments: the files come back as binary properties, named from Attachment Prefix plus an index starting at 0, so attachment_ produces attachment_0.

Lists messages and narrows them down before they enter the workflow, which makes it the reporting operation of the node.

• Return All: on, n8n walks every page of the API; off, Limit caps how many messages come back.
• Search: the Gmail search box syntax, has:attachment for example.
• Received After and Received Before: a date picker, or an expression holding an ISO string or a timestamp in milliseconds.
• Read Status, Sender, Label Names or IDs: the same filters as the trigger, applied on demand.

Flips a message to read without anyone opening Gmail. It belongs at the end of a branch, as the signal that the workflow has done its part.

• Message ID: the message the workflow just handled.

Sends a message back to the unread pile, where a human will see it. The mirror image of the operation above, and it exists for the cases automation should not close.

• Message ID: the message to hand back to a person.

Takes labels off a message, which keeps a mailbox from filling up with tags that meant something two steps ago.

• Message ID: the message to clean up.
• Label Names or IDs: the labels to take off, chosen in the dropdown or passed as IDs with an expression.

Answers inside the existing conversation, so the thread stays in one piece in the recipient's mailbox.

• Message ID: the message being answered.
• Email Type: Text or HTML, and Message holds the body.
• Reply to Sender Only: on, the answer goes to the sender; off, to the whole list of recipients.
• Append n8n Attribution: on by default, it adds the sentence about the email being sent automatically with n8n. Turn it off for customer-facing mail.

Starts a new email from the connected mailbox, outside any existing thread.

• To: one address, or several separated by commas.
• Subject, Message and Email Type: the header line, the body, and Text or HTML.
• Sender Name: the name recipients see in their inbox, which rarely matches the mailbox address.
• CC, BCC, Send Replies To and Attachments: the usual extras, plus files taken from a field of the incoming item.

Sends an email, then pauses the execution until the recipient answers. This is how a human decision gets into an otherwise automatic run.

• Response Type: Approval, where the reader answers from the message; Free Text, for an open reply through a form; Custom Form, for a form you design.
• Type of Approval: Approve Only, or Approve and Disapprove for two buttons.
• Limit Wait Time: caps how long the node waits before the execution resumes on its own.

Creates a label in the mailbox, the filing unit Gmail uses in place of folders.

• Name: the display name, something like invoices.
• Label List Visibility: Show, Hide, or Show If Unread in the label list of the Gmail web interface.
• Message List Visibility: Show or Hide messages carrying that label in the message list.

Removes a label from the mailbox. Worth a second look before running it on a schedule.

• Label ID: the ID of the label, not the name shown in Gmail. A Get Many on labels gives the matching IDs, and an ID that does not exist ends the run on Bad request - please check your parameters.

Returns the detail of one label. Small operation, mostly used as a safety check.

• Label ID: the ID of the label to look up.

Lists the labels of the mailbox with their IDs, which is the quickest way to find the values every other label operation expects.

• Return All: on, every label comes back; off, Limit sets the maximum number returned.

Writes an email into the Drafts folder and stops there. Nothing leaves the mailbox until a person clicks send. That makes it the safest way to automate a reply.

• Subject, Message and Email Type: the draft content, in Text or HTML.
• To Email: optional, so a draft can wait without a recipient.
• Thread ID: attaches the draft to an existing conversation, as in 18cc573e2431878f.
• From Alias Name or ID: the alias the draft goes out from, chosen in the dropdown that loads from the credential, or set with an expression.

Throws away a draft the workflow no longer needs. Housekeeping, but it keeps the Drafts folder from becoming a graveyard.

• Draft ID: the identifier of the draft, which looks like r-3254521568507167962 and has nothing in common with a message ID.

Reads one draft back, attachments included when the workflow asks for them.

• Draft ID: the draft to retrieve.
• Download Attachments: the files arrive as binary data, named from Attachment Prefix plus an index that starts at 0.

Lists the drafts sitting in the mailbox, with the same paging logic as the message operations.

• Return All: on, every draft comes back; off, Limit stops the list.
• Include Spam and Trash: on, drafts filed in Spam and Trash count too.
• Download Attachments and Attachment Prefix: the same binary naming as the single Get.

Labels applied here cover the whole conversation, not just the message that arrived last.

• Thread ID: the Gmail identifier of the conversation, a string like 172ce2c4a72cc243, usually carried over as {{ $json.threadId }} from the previous node.
• Label Names or IDs: pick them from the list n8n reads out of the connected account, or pass label IDs through an expression when an earlier step decides which one applies.

Nothing survives this one: the thread and all its messages go immediately and permanently, and the action cannot be undone. When a way back matters, Trash does the same job without burning the bridge.

• Thread ID: the identifier of the conversation the node operates on, so a wrong value wipes the wrong exchange. Reading the thread first and passing its ID forward is the safe pattern.

Fetching one conversation gives the workflow its messages in a single item, and Simplify decides how heavy that item gets.

• Thread ID: the identifier of the conversation to retrieve.
• Simplify: on by default, it returns a simplified version instead of the raw data, so message IDs, labels and the headers From, To, CC, BCC and Subject. Turn it off for the raw response.
• Return Only Messages: found under Options, it keeps only the messages of the thread in the output.

When a workflow needs a batch of conversations rather than one, this operation lists them and sends one item per thread down the branch.

• Return All and Limit: with Return All on, n8n walks the pages of the Gmail API to the end; off, Limit caps how many threads come back.
• Search: the same syntax as the Gmail search box, has:attachment for example, so a query tested by hand is reusable as is.
• Read Status: unread threads only, read only, or both.
• Received After and Received Before: inside an expression, a date in ISO format or a timestamp in milliseconds.

Tagging is only half the loop. This operation strips labels off a conversation once its state changes, which keeps a filtered Gmail view from filling up with threads nobody has to look at anymore.

• Thread ID: the conversation losing the label, taken from the trigger or from a listing step upstream.
• Label Names or IDs: the labels to take off, chosen in the dropdown or given as IDs through an expression; several can go at once.

A reply sent from here stays inside the existing conversation instead of opening a new one, as recipients expect when the exchange already has a history.

• Thread ID: the conversation the answer belongs to.
• Email Type: Text or HTML, depending on whether the body carries markup.
• Message: the body itself, written in the expression editor when it mixes fixed wording and data from earlier nodes.
• Reply to Sender Only: in Options, it answers the sender alone, while Reply to Recipients Only leaves the sender out; CC, BCC, Sender Name and Attachments sit in the same collection.

Trash moves the conversation and all its messages out of the inbox while keeping them recoverable, which makes it the operation to reach for when a sorting rule might be wrong.

• Thread ID: the conversation to move to the trash, fed by any step upstream that returns a thread.

Sometimes the rule that trashed a conversation was too eager. This operation recovers the thread and all its messages from the trash and puts them back in the mailbox.

• Thread ID: the identifier of the conversation to recover, which is a good reason to store it somewhere when a workflow trashes threads on its own.