SignatoroSignatoro
  • Features
  • Pricing
  • About
  • AI assistantsHelp while you work, when you ask
    • ChatGPT
    • Claude
    • Grok
    • Gemini
    • Copilot
    • Shortwave
    • Fyxer
    AI agentsWork for you on their own
    • Grok Bot
    • OpenAI dots
    • OpenClaw
    • Hermes Agent
    • Manus
    • Cue
    • Meta Muse
    • Claude Duet
    • Poke
    Agentic toolsBuild agents and automations
    • Lindy
    • Notion agents
    • n8n, Zapier, Make
    • Coding agents
    • All AI agents
    Agentic infrastructureWhat agents run on and send through
    • MCP server
    • Signature API
    • Signature API docs
    • Microsoft Agent 365
    • AgentMail
    • Nylas
  • Help
    • FAQ Setup, pricing and deliverability
    • Blog Guides on email signatures and footers
    • Docs Set up your signature in any mail app
    Compare
    • Comparison hub Signatoro next to each per-seat tool
    • Best email signature software How to choose a signature tool
  • Contact
SignatoroSignatoro
One email signature for humans and AI agents. Signatoro is the agentic email signature platform: save your signature once, and your people and every AI agent you connect use the same one.

© Copyright 2026 Signatoro. All Rights Reserved.

  • About Signatoro
  • Automation experts
  • Blog
  • Contact

  • Features
  • Pricing
  • For companies
  • FAQ

  • AI agent signatures
  • ChatGPT
  • Claude
  • Claude Duet
  • Grok Bot
  • OpenClaw
  • MCP server
  • Signature API
  • Agent setup guides

  • Compliance hub
  • AI email disclosure
  • CAN-SPAM
  • GDPR
  • UK company

  • Free tools hub
  • Signature generator
  • Email signature to HTML
  • Signature disclaimer kit
  • Email signature templates

  • All guides
  • Make an email signature
  • Add a signature in Gmail
  • Add a signature in Outlook
  • Add a signature in Apple Mail
  • Add a signature on iPhone

  • Best email signature software
  • All alternatives
  • Signatoro vs Exclaimer
  • Signatoro vs WiseStamp
  • Signatoro vs Newoldstamp
  • Signatoro vs CodeTwo
  • Signatoro vs Opensense
  • Signatoro vs MySignature
  • Signatoro vs Letsignit
  • Signatoro vs Canva
  • Signatoro vs HubSpot generator

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Cookie settings
About
  • About Signatoro
  • Automation experts
  • Blog
  • Contact
Product
  • Features
  • Pricing
  • For companies
  • FAQ
AI agents
  • AI agent signatures
  • ChatGPT
  • Claude
  • Claude Duet
  • Grok Bot
  • OpenClaw
  • MCP server
  • Signature API
  • Agent setup guides
Compliance
  • Compliance hub
  • AI email disclosure
  • CAN-SPAM
  • GDPR
  • UK company
Free tools
  • Free tools hub
  • Signature generator
  • Email signature to HTML
  • Signature disclaimer kit
  • Email signature templates
How to
  • All guides
  • Make an email signature
  • Add a signature in Gmail
  • Add a signature in Outlook
  • Add a signature in Apple Mail
  • Add a signature on iPhone
Compare
  • Best email signature software
  • All alternatives
  • Signatoro vs Exclaimer
  • Signatoro vs WiseStamp
  • Signatoro vs Newoldstamp
  • Signatoro vs CodeTwo
  • Signatoro vs Opensense
  • Signatoro vs MySignature
  • Signatoro vs Letsignit
  • Signatoro vs Canva
  • Signatoro vs HubSpot generator
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Cookie settings
  • In Claude's connector directory
  • In ChatGPT's plugin directory
  • On the Zoho Marketplace
  • Features
  • Pricing
  • About
  • Contact
    1. Home
    2. Blog
    3. AgentMail inboxes now add a signature: what changes for your agents

    AgentMail inboxes now add a signature: what changes for your agents

    Since October 28, 2026, an AgentMail inbox can carry a signature that AgentMail adds to every message it sends. How the setting works, its limits, how it meets a signature your agent already appends, and how to fill it from your saved Signatoro signature.

    By Signatoro Team·Published November 19, 2026·Last updated November 19, 2026·6 min read

    Since October 28, 2026, an AgentMail inbox can have a signature of its own. Set it once on the inbox and AgentMail adds it to every message the inbox sends, through the API, the MCP server or SMTP. An agent that already appends its signature before each send keeps working: AgentMail does not add a signature to a message that already contains it. What changes is where you keep the signature, and that two copies can now drift apart.

    What AgentMail shipped

    AgentMail's changelog entry for October 28, 2026 opens: "Inboxes can now carry a signature that AgentMail adds to every message they send." The inbox docs and the API reference fill in the rules:

    • One setting per inbox. signature is an object with text and an optional html, set when the inbox is created or later with an update. Sending signature: null removes it. The inbox's responses include it when one is set.
    • Every send path. It goes on sends, replies, reply-alls, forwards and drafts, "including scheduled ones", whether they come from the API, the MCP server or SMTP.
    • Placement. "Right after your content, above any quoted or forwarded message."
    • No duplicates. "If your message body already contains the signature, it is not added again."
    • Text and HTML. text goes in the plain-text part. Without html, the HTML part gets text with its line breaks.
    • Size. text is at most 1,000 characters and html at most 4,000, "so link images by URL rather than embedding them."
    • One exception. Visa TAP messages are sent exactly as written, without the signature.

    Before this, AgentMail's send endpoint took a plain-text and an HTML body and had no signature parameter, so the agent had to build the signature into the body itself. Our agent mailbox post described that older behavior, as checked on October 14, 2026.

    What it means for an agent that already signs

    Until October 28, an agent on AgentMail that signed its email had to append the signature to both bodies itself, often fetched right before the send. Three cases follow from AgentMail's rules:

    1. No inbox signature set. Nothing changes. The setting is opt-in, and the inbox sends what the agent built.
    2. Inbox signature set, and it matches what the agent appends. AgentMail sees the signature already in the body and does not add it again. You get one signature.
    3. Inbox signature set, and it differs. The rule is about "the signature", the one stored on the inbox. If the agent appends a newer version and the inbox still holds last month's, the body does not contain the stored one, so AgentMail adds it. The email goes out with two signatures, one of them out of date.

    Case 3 is the one to watch. It happens when someone changes a title or a phone number in one place and not the other. A team that already fetches at send time can leave the inbox setting empty. A team that wants the inbox to sign by itself can turn off the agent's own signature step and keep the inbox copy current.

    Choose where the signature lives

    ApproachWhat signsKeeping it current
    The agent fetches and appends it before each sendThe agent, with the signature fetched for that emailEach send reads the saved version
    AgentMail's inbox signatureAgentMail, on every send path, even when the agent forgetsA copy on the inbox, updated whenever the signature changes
    BothAgentMail skips its copy only when the body contains itTwo copies that must match exactly

    The inbox setting is the safer net for an agent that sometimes skips a step. Fetching at send time keeps one source of truth and works on any mailbox the agent moves to.

    Fill the inbox signature from Signatoro

    If you keep your agents' signatures on Signatoro, the agentic email signature platform, you can copy one into the AgentMail inbox the agent sends from. Add the agent on Signatoro first, as a company AI agent or one of your AI assistants, with its own API key.

    1. Fetch the agent's signature with its own key:

      GET https://signatoro.com/api/v1/signature
      Authorization: Bearer <the agent's Signatoro key>
      

      A key bound to an agent always returns that agent's signature, as html and text.

    2. Check the length. AgentMail allows up to 4,000 characters of html and 1,000 of text. A designed signature built from tables and inline styles can be long, so check yours before you store it. Pictures already sit at a public web address, the form AgentMail asks for.

    3. Store it on the inbox with an update, in code that passes the two values straight through:

      PATCH https://api.agentmail.to/v0/inboxes/<inbox address>
      Authorization: Bearer <your AgentMail key>
      Content-Type: application/json
      
      {"signature": {"text": "<text from step 1>", "html": "<html from step 1>"}}
      

      Pass them from the response in code, never retyped by a model: Signatoro's replies say so too.

    4. Run it again after every change to the agent's signature: a new title, a new logo, a new AI line. Signatoro's webhooks post an event when a person's signature changes, but they do not cover AI assistants' or company agents' signatures yet, so trigger the update yourself, for example from the job that changes it, or on a schedule.

    5. Send one test email from the inbox and read it as the recipient sees it: one signature, the right phone and email address.

    If the signature is too long for the inbox setting, or you would rather not keep a second copy, keep fetching at send time and leave the inbox setting empty. The AgentMail page and the email API guide show that route.

    One signature for every agent inbox

    Give each agent its own name, role and AI line on Signatoro, and fetch it with the agent's own key, at send time or into the inbox setting.

    Set up an AI agentSee pricing

    Frequently asked questions

    Does AgentMail support email signatures now?

    Yes, since October 28, 2026. An inbox can carry a signature with text and an optional html, and AgentMail adds it to sends, replies, reply-alls, forwards and drafts from the API, the MCP server and SMTP.

    Will my agent's emails get two signatures?

    Not if the inbox setting is empty, and not if the agent appends exactly the signature stored on the inbox. They can if the two differ: AgentMail skips its copy only when the body already contains it.

    Can each agent have its own signature?

    The setting is per inbox, so each agent with its own inbox can carry its own. Several agents sending from one inbox share that inbox's signature, unless each appends its own and the inbox setting stays empty.

    Can an AgentMail signature include a logo?

    Yes, as a picture linked by URL in html. AgentMail's docs say to link images rather than embed them, because html is limited to 4,000 characters.

    Does the inbox signature change when I edit my signature on Signatoro?

    No. The inbox holds a copy. Update it after each change, or skip the copy and let the agent fetch the signature before each send.

    Sources

    Read on November 9, 2026:

    • Changelog, October 28, 2026 entry (AgentMail docs)
    • Inboxes: Signatures (AgentMail docs)
    • Update Inbox, InboxSignature (AgentMail API reference)
    • What can I do with an AgentMail inbox? (AgentMail knowledge base)

    One footer for the whole team

    Set it once for the company and every member's signature carries it. See plans by team size.

    Create my company

    One footer for the whole team

    Set it once for the company and every member's signature carries it. See plans by team size.

    Create my company

    Related posts

    • Google's coworker agents get their own email address: what will they sign with?
    • Grok Bot now adds your Gmail signature to drafts: what changed in October
    • Signatoro is in ChatGPT's plugin directory