Skip to main content

Documentation Index

Fetch the complete documentation index at: https://documentation.outpost.pub/llms.txt

Use this file to discover all available pages before exploring further.

Email templates are the building blocks for all Outpost email communication. A template defines the subject line and body of an email, with merge fields for personalization. Templates are reused across autoresponder flows, campaigns, and the failed payment flow.
Email Templates list with search, export, and expandable row previews

​
Template list

The Email Templates page displays all your templates in a searchable table:
ColumnDescription
DateWhen the template was created
NameInternal name for organizing templates
SubjectThe email subject line
ActionsEdit or delete the template
Click a row to expand it and see an HTML preview of the template body. Use the Export button to download your template list.

​
Creating a template

Go to Email Templates in the left navigation and click New Email Template. The form opens with the title Add Notification Email Template.
FieldDescription
Template NameInternal label for organizing templates. Required.
SubjectThe email subject line. Merge fields supported. Required.
OfferOptionally link an offer — this enables the %OFFER_URL% merge field to generate personalized checkout links.
Email Body TextThe email body content. Use the rich text editor to format text, add images, links, and merge fields.

​
Merge fields

Merge fields let you insert dynamic content into your email templates. Wrap the field name in % characters — for example, %SUBSCRIBER_FIRST_NAME%.
Merge fields work in both the subject line and the email body.

​
Fallback values

Some merge fields support a fallback value that displays when the member’s data is empty. Outpost supports two fallback formats: Single-word fallback — Add a | after the field name followed by the fallback word: 
Hey %SUBSCRIBER_FIRST_NAME%|there, thanks for subscribing!
The pipe format only uses the first word after |. So %SUBSCRIBER_FIRST_NAME%|there friend falls back to just “there”, not “there friend”. Multi-word fallback — Use the ,fallback="..." syntax with double or single quotes to allow spaces: 
Hey %SUBSCRIBER_FIRST_NAME%,fallback="dear friend", thanks for subscribing!
You can also use the comma syntax without quotes for a single word: %SUBSCRIBER_FIRST_NAME%,fallback=there. If the member’s first name is “Alex”, both examples render as “Hey Alex, thanks for subscribing!” — but if the first name is blank, the first renders as “Hey there, …” and the second as “Hey dear friend, …”. Fallback values work with: %SUBSCRIBER_FIRST_NAME%, %SUBSCRIBER_FULL_NAME%, and %SUBSCRIBER_EMAIL_ADDRESS%.
Outpost automatically scans action templates, advanced autoresponder flows, and active campaigns for malformed fallback patterns — common typos like %VAR|there% (missing % before the pipe), %VAR%| (empty fallback), or %VAR%,fallback="unclosed (unclosed quote) get surfaced as warnings so you can fix them before sending.

​
Member fields

FieldDescription
%SUBSCRIBER_FIRST_NAME%Member’s first name. Supports fallback syntax.
%SUBSCRIBER_FULL_NAME%Member’s full name. Supports fallback syntax.
%SUBSCRIBER_EMAIL_ADDRESS%Member’s email address. Supports fallback syntax.
%SUBSCRIBER_TIER_NAME%Name of the member’s current subscription tier
%UNSUBSCRIBE_URL%Member’s email unsubscribe link
%MEMBER_GHOST_GUID%Member’s unique identifier

​
Site fields

These fields pull from your publication’s settings. The BLOG_ and SITE_ prefixed versions produce the same output — use whichever you prefer.
FieldDescription
%SITE_NAME% / %BLOG_NAME%Your publication name
%SITE_URL% / %BLOG_URL%Your publication URL
%SITE_PATH% / %BLOG_PATH%Your publication path
%SITE_LOGIN_URL% / %BLOG_LOGIN_URL%Your member sign-in page URL
%ACCOUNT_LINK%Member account management page URL
%EMAIL_FROM_NAME%The sender name configured in your email settings
%CURRENT_DATE%Today’s date (formatted as “March 15, 2026”)

​
Subscription and billing fields

FieldDescription
%RENEWAL_PRICE%The member’s next renewal price (number only)
%RENEWAL_PRICE_WITH_CURRENCY%The member’s next renewal price with currency symbol
%CURRENCY%The member’s subscription currency code (e.g. USD)
%BILLING_PERIOD%The billing interval — “monthly”, “yearly”, etc.
%BILLING_PERIOD_CAPITALIZED_FIRST_LETTER%Billing interval with first letter capitalized — “Monthly”, “Yearly”
%BILLING_CADENCE%Billing cadence text — “month”, “year”, etc.
%BILLING_CADENCE_CAPITALIZED_FIRST_LETTER%Billing cadence with first letter capitalized — “Month”, “Year”
%SUBSCRIPTION_EXPIRATION_DATE%When the current subscription period ends
%SUBSCRIPTION_EXPIRATION_PLUS_1YEAR_DATE%One year after the current expiration date
%TRIAL_END_DATE%When the member’s trial period ends (only available for trialing members)
%END_TRIAL_PRICE%The price the member will be charged when their trial ends
FieldDescription
%OFFER_URL%A personalized checkout link for the offer attached to this template or action. Requires an offer to be linked.
%UPDATE_PAYMENT_METHOD_URL%Link for the member to update their payment method on file

​
Complimentary subscription fields

These fields are only available in templates used by complimentary subscription actions (e.g., renewal reminders for comped members).
FieldDescription
%RENEW_COMPLIMENTARY_SUBSCRIBER_URL%Link for a comped member to confirm they want to renew
%DO_NOT_RENEW_COMPLIMENTARY_SUBSCRIBER_URL%Link for a comped member to decline renewal

​
Gift subscription fields

These fields are only available in templates used by gift subscription actions. They are populated from the gift subscription record.
FieldDescription
%GIFT_GIVER_NAME%Name of the person who purchased the gift
%GIFT_GETTER_NAME%Name of the gift recipient
%GIFT_SUB_MESSAGE%The personal message the giver included with the gift
%RENEW_GIFT_URL%Link for the gift giver to extend the gift subscription
%DO_NOT_RENEW_GIFT_URL%Link for the gift giver to let the gift expire

​
Group subscription fields

These fields are only available in templates used by group subscription invite actions.
FieldDescription
%GROUP_SUBSCRIPTION_BUYER_EMAIL%Email of the group subscription owner
%GROUP_SUBSCRIPTION_BUYER_NAME%Name of the group subscription owner
%GROUP_SUBSCRIPTION_INVITE_URL%Invite link for the recipient to accept the group seat
%GROUP_SUBSCRIPTION_RECEIVER_EMAIL%Email of the invited group member

​
Gated PDF fields

These fields are only available in CTA gated PDF delivery emails.
FieldDescription
%PDF_URL%Download link for the gated PDF file

​
Conditional content blocks

Show or hide sections of your email based on whether the member is on a free or paid plan: 
%RECIPIENT.PAID_BLOCK_START%
This content is only visible to paid members.
%RECIPIENT.PAID_BLOCK_end%

%RECIPIENT.FREE_BLOCK_START%
This content is only visible to free members.
%RECIPIENT.FREE_BLOCK_END%
Note the casing difference: the paid block closing tag uses lowercase end (%RECIPIENT.PAID_BLOCK_end%) while all other tags use uppercase. This must match exactly or the block won’t render correctly.
Use these blocks to include upgrade CTAs for free members while showing thank-you messages or exclusive content links for paid members — all within a single template.
The block tags must be on their own lines. Do not nest paid blocks inside free blocks or vice versa.

​
Offer templates

If a template is linked to an offer, the %OFFER_URL% merge field generates a personalized URL that takes the member directly to checkout with the offer pre-applied. This is used for:
  • Win-back campaigns to bring cancelled members back at a discount
  • Renewal reminder emails with a one-click resubscribe link
  • Upgrade offers for free members
The offer dropdown shows both regular offers and subscription plans.

​
Preview and test

Before using a template in a flow or campaign:
  1. Click Send Test Email to send a real email to your own address with actual merge field values.
  2. If the template has unsaved changes, the button label switches to Send Test Email before saving changes as a reminder to save first.
  3. Check the email in both desktop and mobile email clients before activating.

​
Special action templates

Some templates are linked to specific built-in autoresponder actions (such as card expiration reminders or offer click reminders). These templates show a warning in the editor indicating they are connected to built-in automations.

Email Design Settings

Customize colors, fonts, header image, and custom HTML for all email templates.

Autoresponder

Use templates in automated email sequences.

Campaigns

Send templates as one-time campaigns to targeted segments.

Offers & Discounts

Link offers to templates for personalized checkout links.

​
FAQ

Yes. The email body editor supports rich text and HTML. For full control over the email layout, you can also set a custom HTML template in Email Design Settings.
Use merge fields in the subject field — for example, Hey %SUBSCRIBER_FIRST_NAME%, we miss you! will insert the member’s first name.
If a member’s first name is empty, %SUBSCRIBER_FIRST_NAME% will render as an empty string. Use the fallback syntax to handle this gracefully: Hey %SUBSCRIBER_FIRST_NAME%|there (single word) or Hey %SUBSCRIBER_FIRST_NAME%,fallback="dear reader" (multi-word) will render the fallback when the name is blank.
Yes. Templates are standalone and can be referenced by any number of autoresponder flows or campaigns.