Your email signature lives in your mail app's compose window. Gmail and Outlook add it when you write an email there, and nowhere else. A CRM, a help desk or a support inbox that sends through the Gmail API, Microsoft Graph or SMTP builds the email itself, so the email ends where the app's text ends: no name, no title, no company details.
Teams keep running into this, and they say so in public. Four feature requests from 2026, in four open-source products, describe the same gap.
Four teams, one missing signature
Twenty, the open-source CRM. A request titled "Append the sender's email signature to outbound emails" opened in June and has more than a dozen upvotes. When a user sends from Twenty, from the record composer, the AI send-email tool or a workflow, "the email arrives without their signature", because "a Gmail signature is applied only by the Gmail web/mobile compose UI". The proposed fix reads the default Gmail signature, and a reply asks for more: "We don't use gmail and would like this feature."
PostHog Support. A request to "add configurable signatures to outbound email replies" notes that signatures set in Google Workspace or Gmail are not applied, so every reply lacks the company and sender details "unless an agent manually pastes it". An open pull request adds a plain-text signature for each person.
Chatwoot. An account-level default signature request counts it out: on one account, 14 of 33 support agents had set a signature, "all 14 are the same block copied from a colleague, with drift": broken links, photos stored in the wrong place, missing lines. New agents start with nothing.
Frappe Helpdesk. A team using the new signature feature wants a different logo per team, because some people work on several teams and the signature should match the hat they wear.
Commercial CRMs too
The same gap shows up in the big CRMs, in their own documentation and community answers:
- HubSpot. A workflow's emails are marketing emails, and a user who asked why their signature was missing from one was told that the signature setting is for one-to-one emails. HubSpot's fix is a Contact owner signature token placed in the email.
- Salesforce. Salesforce's documentation for the Flow "Send Email" action says those emails don't include signatures from My Email Settings, so the signature has to sit in the template, as a Trailblazer thread quotes.
- Zoho CRM. When an admin sends a mailing from an organization address, the user's own signature is not merged in, and the user asking did not want to hardcode it into the template.
In Twenty, a second request for the same thing, a default signature per account that each member can override, was closed in October as a duplicate of the first.
What they have in common
- The app sends, so the app has to sign. Each product sends through an API or SMTP, which never sees the signature saved in Gmail or Outlook.
- Every fix stores another copy. A signature setting inside the CRM, another inside the help desk, a third in the mail app. Each copy is edited by hand, and each one drifts, which is the Chatwoot count above.
- Teams need the details to be right. The PostHog and Chatwoot requests both point to rules in Europe about the company details a business email carries, so a missing or stale signature can leave out details a business has to show.
- AI sends too. Twenty's AI send-email tool and AI-drafted support replies go out through the same path, with the same missing signature.
The fixes on offer
Wait for each app's own signature setting. It works inside that app, from the day it ships. You keep one more copy to update, per person and per app, and the copies stay separate from the signature people use in Gmail or Outlook.
Paste the signature into each app's template. It is quick for one sender, and it stays as it was until someone pastes again, in every template that holds it.
Fetch one saved signature at send time. Keep the signature in one place and have every app fetch it just before it sends. A change made once reaches the next email from every app, and people, help desks, CRMs and AI agents send the same signature.
That third option is what Signatoro is for: save the signature once, and every tool that sends fetches it from Signatoro's API or MCP server, as HTML and as plain text. In Twenty it takes two workflow steps, an HTTP Request that fetches the signature and the Send Email action that adds it after the message. The Twenty guide has the steps.
Plain text or HTML?
Some apps escape HTML that arrives from outside. Twenty's workflow email escapes HTML inside a variable, so the plain-text signature is the one to use there: name, role, company, phone and links, each on its own line. In our test on October 25, 2026, the HTML version arrived in the inbox as code, and the plain-text version arrived clean. Apps that build the whole message in code, such as a Gmail API script or an n8n workflow, can send the HTML signature with its logo and photo. Check one test email in each app before you rely on it.
Questions
Why does my CRM send emails without my Gmail signature?
Gmail adds your signature in its own compose window. A CRM that sends through the Gmail API hands Gmail a finished message, and the Gmail API sends it as it is, without adding the signature.
Should each person keep a signature in every app?
It works for a small team that rarely changes details. Each copy needs its own update, so a new title, phone number or logo has to be changed in every app that holds one.
Does this apply to AI agents?
Yes. An AI agent that sends through a connector or an API skips the compose window too. The post on why emails your AI agent sends have no signature covers the fix for each AI tool. For HubSpot, see the HubSpot guide.
Sources
Read on October 25, 2026:
- Append the sender's email signature to outbound emails (Twenty discussion #21194)
- Support: add configurable signatures to outbound email replies (PostHog issue #76937)
- feat(conversations): let each agent set their own email signature (PostHog pull request #115714)
- Account-level default message signature template with agent placeholders (Chatwoot issue #15883)
- Email signature cannot be templated (Frappe Helpdesk issue #3397)
- Email signatures: a default signature per account/alias (Twenty issue #27225)
- Workflow From Address & Signature (HubSpot Community)
- Bug in core Send Email action? (Salesforce Trailblazer Community)
- When I use an organization email, how can I get the user's signature? (Zoho Community)
- resolve-email-body.util.ts (Twenty source)