Airpost
Using Airpost

Templates and signatures

Reuse messages you send often, add signatures per account and alias, and manage both from the CLI.

Templates and signatures are both stored on your computer and shared by every Airpost surface: the desktop composer, the CLI, the MCP server and the web client all read the same ones.

Templates

A template is a message you send often, like a meeting follow-up or a support answer, with optional variables you fill in each time.

Create a template

Open Templates

Go to Preferences > Templates and click + New template. You can also write a draft and choose Save Draft as Template… from the templates menu in the composer.

Name it and write it

Give it a Name and, optionally, a Subject. Names can use letters, digits, spaces, - and _.

Tag the parts that change

Select text you change each time, like the recipient’s name, and click the tag icon in the toolbar to turn it into a variable.

When you save a draft as a template, Airpost keeps only what you wrote: the signature and quoted text below it are left out.

Use a template

In the composer, click the templates icon next to the Send button and pick a template.

  • The template’s text replaces what you wrote above your signature and the quoted message. Your signature and the quote stay. If the draft already has text, Airpost asks before replacing it.
  • On a new message, the template’s subject fills in the subject. On a reply or forward, the subject is left as it is.
  • Press Tab to jump between the tagged variables and fill them in. The highlighting is removed when you send, so recipients never see it.

Where templates are stored

Each template is one HTML file, <name>.html, in the templates folder of your profile. The subject is a <meta name="subject" content="..."> line at the top of the file. Variables are <span data-tvar="name"> elements.

Show templates folder in Preferences > Templates opens it. Airpost watches the folder, so you can add or edit files with any editor, sync the folder yourself, or keep it in git, and the composer picks up changes immediately.

templates/Follow up.html
<meta name="subject" content="Following up on our call"/>
<p>Hi <span data-tvar="name">there</span>,</p>
<p>Thanks for your time today. As promised, here's the summary.</p>

Signatures

Go to Preferences > Signatures and click + New signature.

FieldWhat it does
NameIdentifies the signature in menus
Default forThe accounts and aliases that start new mail and replies with it
StyleA layout that builds the signature from Details such as your name, title, phone, website, photo and social links. Choose HTML to write it yourself instead

Each address, including each alias, has at most one default signature. An address without one starts without a signature.

In the composer, the signature follows the From address: change From and the signature changes to that address’s default. You can also switch or remove the signature for the current message from the signature menu, or choose Edit Signatures… to open Preferences.

The signature goes above the quoted text in replies and forwards, and is kept as its own block in the draft, so switching or removing it doesn’t touch what you wrote.

From the CLI

# Templates
airpost template list
airpost template show "Follow up"
airpost template save "Follow up" --subject "Following up on our call" \
  --body "Hi {{name}}, thanks for your time today."
airpost template save --from-draft <draft-id>      # as Save Draft as Template does
airpost template delete "Follow up"

# Start a draft from a template, then fill its variables
airpost draft new --to ann@example.com --template "Follow up"
airpost draft edit <draft-id> --body "Hi Ann, thanks for your time today."

# Signatures
airpost signature list
airpost signature set Work --body-file ~/work-signature.html --html
airpost signature default Work --for me@example.com --for me@alias.example.com
airpost signature default none --for me@example.com

In template save, {{name}} in the text becomes a variable. A name that’s taken gets a number added unless you pass --replace. draft new, reply, reply-all and forward all take --template, and add the signature the composer would.

Agents can list templates with the MCP list_templates tool and draft from them. See Agent tools.