If emails from your n8n workflow end with "This email was sent automatically with n8n", the node is doing what it does by default. n8n's Gmail and Send Email nodes add that line unless you turn off an option called "Append n8n Attribution". Turning it off takes a minute. The email then ends with no signature at all, because n8n does not use the signature saved in Gmail or Outlook, so the second half of this guide puts your real signature where n8n's line was.
The quick fix
- Open the node that sends the email: Gmail (Send or Reply), Send Email, or a "Send and Wait for Response" step.
- Under Options, select Add option.
- Choose Append n8n Attribution.
- Turn the toggle off.
- Click Publish so the change reaches your live workflow, then check a real sent email.
These steps follow n8n's own Gmail node troubleshooting page. Step 5 matters since n8n 2.0, as explained below.
Which n8n nodes add the line
n8n's docs describe the option on each node that sends email:
- Gmail node, Send and Reply. "By default, the node appends the statement
This email was sent automatically with n8nto the end of the email. To remove this statement, turn this option off." (Gmail message operations) - Send Email node (SMTP). The node's options include "Append n8n Attribution", to "include the phrase This email was sent automatically with n8n at the end of the email (turned on) or not (turned off)." The same option appears for its "Send and Wait for Response" operation. (Send Email)
- Microsoft Outlook node, Send and Wait for Response. n8n lists "Append n8n Attribution" among the options for this operation. (Microsoft Outlook)
In an HTML email from the Gmail node, n8n's source code puts the line in italics under a short divider, with "n8n" linked to n8n's website.
Still seeing "sent automatically with n8n"?
Publish the workflow again. Since n8n 2.0, edits are saved as a draft and the live workflow keeps running the last published version. n8n's docs say: "Production executions will use this published version, not your latest edits." If the line disappears when you test in the editor but comes back when the workflow runs on its own, this is the likely reason. Click Publish in the canvas header (or press Shift + P). (Save and publish workflows)
Check every node that sends. A workflow with a reply branch, an error branch or a "Send and Wait for Response" approval step has more than one sending node, and each has its own toggle.
Check AI Agent tools. When the Gmail node runs as a tool for n8n's AI Agent node, check the option on the tool node as well. Users in n8n's community report that the line can still appear on AI Agent and MCP workflows with the option off. If that happens to you, give the option a fixed "off" value in the tool and send yourself a test; the workaround posted in that thread patches n8n's source files and, by its author's account, has to be redone after updates.
Add your real signature instead
Removing n8n's line leaves the email ending wherever the message body ends. Google's Gmail API reference describes the Gmail signature as "included in messages composed with this alias in the Gmail web UI", and n8n's Gmail node sends through that API, so your Gmail signature is not added. One n8n user described it this way: "I have a signature set on my gmail account, but it is not used when sending emails with the gmail node." The same goes for Outlook and SMTP sends.
You can paste your signature's HTML into the node, or fetch it on every run so a change to your signature reaches the workflow without editing it:
- Save your signature on Signatoro (make one free from the generator if you need it). On the signature page, under "For tools and assistants", click "Generate API key".
- Add an HTTP Request node before the sending node: method GET, URL
https://signatoro.com/api/v1/signature. - For authentication, choose the generic credential type Bearer Auth and save your Signatoro API key in it. Keep the key in the credential, out of prompts and node fields.
- In the Gmail node, set Email Type to HTML; in the Send Email node, set Email Format to HTML.
- In the message body, put your text, then map the HTTP Request node's
htmlfield after it. - Turn off Append n8n Attribution, publish, and send yourself a test.
For a plain-text email, map the text field instead. Signatoro's n8n, Zapier and Make guide has the same steps for Zapier and Make, and the signature API guide has the full response.
When an AI agent writes the email
If an AI Agent node writes the email, let the model write the body only. Build the message field as an expression that puts the HTTP Request node's html after {{ $fromAI('body') }}, so the signature comes from a fixed source every time and the model never invents one. Why AI agent email arrives with no signature explains the same problem across ChatGPT, Claude and other agents.
If your workflow sends email on your behalf without a person reviewing it, consider saying so in the signature. Some rules now expect it: AI email disclosure covers when and how.
n8n email signature questions
How do I remove "This email was sent automatically with n8n"?
In the Gmail or Send Email node, open Options, select Add option, choose Append n8n Attribution and turn it off. Then publish the workflow, because since n8n 2.0 the live workflow runs the last published version until you publish again.
Why does the n8n attribution still appear after I turned it off?
Most often, the change was saved but not published, so production runs still use the old version. Other causes are a second sending node that still has the option on, or a Gmail node used as an AI Agent tool, where users report the line can persist. Publish, check every sending node, and test with a real email.
Is there any way to force n8n to send emails with my signature?
Yes, by putting the signature in the email yourself. n8n's Gmail node sends through the Gmail API, which does not add the signature saved in Gmail. Set the email type to HTML and add the signature after the body, pasted in or fetched on every run from Signatoro's API with an HTTP Request node.
Why doesn't my signature image show up in emails sent from n8n?
n8n's Gmail node does not add the signature saved in Gmail, so its image never makes it into the email. Fetch the signature's html from Signatoro's API in an HTTP Request node and map it into the message: Signatoro's signature API guide lists n8n's mail nodes among the send paths that keep the picture.
Does n8n add the attribution to Outlook emails?
n8n's docs list "Append n8n Attribution" for the Microsoft Outlook node's "Send and Wait for Response" operation. For its other send operations, the docs list no such option.
Sources
Checked on October 7, 2026:
- n8n Docs: Gmail node common issues
- n8n Docs: Gmail node message operations
- n8n Docs: Send Email
- n8n Docs: Microsoft Outlook node
- n8n Docs: Save and publish workflows
- n8n Docs: HTTP Request credentials
- n8n Community: This email was sent automatically with n8n, January 2026
- n8n Community: Using a gmail signature, November 2025
- Google: REST Resource: users.settings.sendAs (Gmail API)