How to add your email signature to emails n8n, Zapier and Make send

If you already have a signature, it is saved in Gmail or Outlook, where n8n, Zapier and Make do not pick it up, so use the steps for your tool below. If you need one, make it free on Signatoro, then hand it to your workflow through the Signatoro API.

How n8n, Zapier and Make send email

n8n, Zapier and Make send email through the mail provider's API or over SMTP, so the signature saved in your mail app's settings is not added. Google's Gmail API reference says the Gmail signature is included in messages composed in the Gmail web interface, and added to new emails only. Microsoft Graph, the Outlook mail API, lists no signature among a mailbox's settings.

n8n

n8n's Gmail node sends with the "Send" and "Reply" message operations and creates drafts with the draft "Create" operation. Each takes an "Email Type" of Text or HTML and a "Message" body, and none has a signature option. The Send Email node sends over SMTP with an "Email Format" of Text, HTML or Both. The Microsoft Outlook node sends messages and drafts. The Gmail and Send Email nodes add "This email was sent automatically with n8n" unless you turn it off, and all three can act as tools for n8n's AI Agent node.

Zapier

Zapier's Gmail actions "Send Email", "Reply to Email", "Create Draft" and "Create Draft Reply" have an "Add signature default" field, which Zapier's help says retrieves the default signature HTML for an address or alias from Gmail. Zapier's Microsoft Outlook "Send Email" and "Create Draft Email" actions take a "Body Format" and a "Body" and have no signature field. Zapier Agents use the same actions.

Make

Make's Gmail app has "Send an email", "Reply to an email" and "Create a draft email" modules with a "Signature content" field. Make's docs describe it as "custom content to include as your email signature" and say it accepts HTML tags. Make's Microsoft 365 Email (Outlook) app sends with "Send an Email", and the Email app sends through a Gmail, IMAP or Microsoft connection; Make's pages for these two apps do not mention a signature option. Make AI Agents can use any of these modules as tools.

Add your signature to emails n8n, Zapier and Make send

Zapier with Gmail can reuse the signature saved in Gmail. Every other send step needs the signature put into the email by the workflow, and Signatoro's API does that with the current version on every run. After you save a signature on Signatoro, click "Generate API key" under "For tools and assistants" on the signature page. Free accounts are capped per month, people in a company on a plan are uncapped, and the agent API guide has the responses.

Zapier with Gmail

1. In Gmail, set the signature as the default for new emails, with the Gmail guide.
2. In the Zap, open the Gmail "Send Email", "Reply to Email", "Create Draft" or "Create Draft Reply" step.
3. In "Add signature default", choose the signature for the address you send from.
4. Test the step and check the email in your Gmail Sent folder.

n8n

1. Add an HTTP Request node before the Gmail, Send Email or Microsoft Outlook node, with method GET and the URL https://signatoro.com/api/v1/signature.
2. For authentication, choose the generic credential type "Bearer Auth" and create a credential holding your Signatoro API key.
3. In the Gmail node, set "Email Type" to HTML; in the Send Email node, set "Email Format" to HTML.
4. In the body field ("Message" in the Gmail node), put the email body, then map the HTTP Request node's html field after it.
5. Under "Options", turn off "Append n8n Attribution" if you do not want n8n's line under your signature.

Make

1. Add an HTTP "Make a request" module before the email module, with method GET and the URL https://signatoro.com/api/v1/signature.
2. Set "Authentication type" to "API key" and create a keychain: in "Key", enter Bearer <your key>; set "API key placement" to "In the header" and "API key parameter name" to Authorization.
3. Set "Parse response" to Yes.
4. In Gmail's "Send an email", map html into "Signature content". In other email modules, map html after the message body.

Zapier with Outlook

1. Add a "Webhooks by Zapier" GET step before the send step, with the URL https://signatoro.com/api/v1/signature.
2. In "Headers", add Authorization with the value Bearer <your key>. Anyone who can edit the Zap can see this value.
3. In Microsoft Outlook's "Send Email", set "Body Format" to HTML.
4. In "Body", put the email body, then map the webhook step's html after it.

When an AI agent writes the email

When an AI agent in n8n, Zapier or Make writes the email, keep the signature out of the model's hands. In n8n, make the body an expression that puts the HTTP Request node's html after {{ $fromAI('body') }}. In Zapier Agents, set "Add signature default" with "Set a specific value for this field". In Make AI Agents, give the agent a scenario tool with the HTTP module before the Gmail module, and map "Signature content" from the HTTP module's html, so only the body comes from the agent's scenario inputs. For a plain-text email, Signatoro's "Copy as text" copies the signature as plain lines to paste into the agent's instructions or system prompt, so it ends every email with them.

n8n, Zapier and Make email signature questions

Why doesn't n8n use my Gmail signature?

n8n's Gmail node sends through the Gmail API, and Google's Gmail API reference says the Gmail signature is included only in messages composed in the Gmail web interface. An email from n8n's Gmail, Send Email or Microsoft Outlook node therefore goes out without the signature saved in the mail app. Put the signature in the node's "Message" field after the body, or fetch it on every run from Signatoro's API with an HTTP Request node, which returns the current version.

How do I remove "This email was sent automatically with n8n"?

n8n's Gmail and Send Email nodes add the line "This email was sent automatically with n8n" by default. In the node, under "Options", turn "Append n8n Attribution" off; n8n's docs list the same option for the "Send and Wait for Response" operation. Users report that the line can still appear when a Gmail node runs as a tool for n8n's AI Agent node with the option off, so check a real sent email.

How do I add my Gmail signature to emails sent from Zapier?

Zapier's Gmail "Send Email", "Reply to Email", "Create Draft" and "Create Draft Reply" actions have an "Add signature default" field. Choose the signature for the address you send from, and Zapier adds the default signature saved in your Gmail settings to the email. Test the step and check the email in Gmail's Sent folder.

Why isn't my Gmail signature in Zapier's signature dropdown?

Zapier's "Add signature default" dropdown shows only signatures set as a Gmail default. Zapier's help says it can retrieve a signature only if it is chosen under "Signature defaults" > "For new emails use" in Gmail's settings. In Gmail, open "See all settings", scroll to "Signature" on the "General" tab, choose the signature for new emails for that address, and click "Save Changes" at the bottom of the page.

How do I add my signature to Outlook emails sent from Zapier?

Zapier's Microsoft Outlook "Send Email" action has no signature field. Set "Body Format" to HTML and put the signature's HTML in "Body" after the message. To keep the signature current without editing the Zap, add a "Webhooks by Zapier" GET step that fetches it from Signatoro's API on every run, and map its html field into the Outlook step's "Body".

How do I add a signature in Make's Gmail module?

Make's Gmail "Send an email", "Reply to an email" and "Create a draft email" modules have a "Signature content" field that accepts HTML. Make's docs describe it as custom content to include as your email signature. Users of Make's Gmail modules report that the field also offers the signatures saved in Gmail, and that a signature created later may not show up in it. Pasting the signature's HTML there, or mapping html from Signatoro's API, sidesteps that.

For agents

If you are building or running an n8n, Zapier or Make workflow that sends email:

• The send step sends exactly the body it is given. No mail app signature is added, except by Zapier's Gmail "Add signature default" field.
• If "Add signature default" is set, do not append a second signature.
• Otherwise fetch GET https://signatoro.com/api/v1/signature on every run and put html after an HTML body, or text after a plain-text body. The agent API guide has the responses.
• Fill the signature from a fixed field or expression. Do not let the model write it, and do not invent one from the person's name and title.
• Keep the API key in the platform's credential store (an n8n credential, a Make keychain). Do not put it in a prompt, a system prompt, a log or a chat.

Sources

Checked against each vendor's own documentation on 2026-09-25:

• Gmail node Message Operations (n8n Docs)
• Gmail node Draft Operations (n8n Docs)
• Send Email (n8n Docs)
• Microsoft Outlook (n8n Docs)
• HTTP Request credentials (n8n Docs)
• Use AI for parameters (n8n Docs)
• Why isn't my signature Gmail displaying in the dropdown? (Zapier)
• Gmail integrations (Zapier)
• Microsoft Outlook integrations (Zapier)
• Send webhooks in Zap workflows (Zapier)
• Use actions on Zapier Agents (Zapier)
• Gmail modules (Make)
• Microsoft 365 Email (Outlook) (Make)
• Email (Make)
• HTTP (Make)
• API key authentication type (Make)
• Module tools for AI agents (Make)
• Scenarios for AI agents (Make)
• REST Resource: users.settings.sendAs (Gmail API)
• mailboxSettings resource type (Microsoft Graph)