Tokens are little fill-in-the-blank labels. Add one to a supported template, and Moxie replaces it with the matching information when that template is used.

Hi {{Contact.First}}, your invoice {{Invoice.Number}} is ready.

With Jamie and invoice INV-1042 in the flow, this becomes:

Hi Jamie, your invoice INV-1042 is ready.

How scope works

Think of each flow as carrying a small folder. An invoice email has an invoice in its folder. A meeting reminder has an appointment. A portal page knows which contact is signed in.

A token can only use information in that folder. That is all “scope” means.

A client email can fill in a client name, but it cannot guess which of that client’s invoices you mean.
A meeting reminder can fill in the appointment time once it has a booked meeting.
A package description can show that package’s price because it knows which package it belongs to.
A workflow may gain more information as steps create or connect records. A token for a future invoice cannot fill in before that invoice is available to the step.

A token needs three things: the field you are editing must support it, the flow must have the right record, and that record must have a value. Simply owning a record somewhere in Moxie does not put it into every flow.

How to use this reference

Copy the whole token, including both pairs of braces: {{Client.Name}}. Match the spelling and capitalization exactly; do not add spaces inside the braces.
Use the token picker where available. Some pickers show possibilities for a reusable template before a particular client, invoice, or meeting has been chosen.
The Tags column shows where a token can be used when its context is available. A tag is not a promise that every screen or every step in that module supports it.
Email means supported email-template flows. Workflows means steps that receive the required record. Invoice layouts and Agreement documents mean the document content itself. Portal pages means custom client-portal pages. Project templates means creating a project from a template.
A link token gives you a URL. Use it as the destination of a link or button in editors that support that feature.
Money and dates usually follow the currency and display settings for the relevant record or flow. ISO means a consistent saved date format; it does not make a token available in additional places.

Two spellings to watch: {{Meeting.Timezone}} is for booked-meeting messages; {{Meeting.TimeZone}} is for booking-page text. Also, {{Invoice.LateFee}} means a fee amount in invoice emails/workflows, but a percentage in invoice layouts.

Your business

These values come from your workspace’s business details. The flow must support business tokens; being signed in does not make them available in every editor.

Token	Populated value	Tags
`{{Account.Name}}`	Your business name.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Email}}`	Your business email address.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.TaxId}}`	Your business tax ID.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Address1}}`	Your business address, line 1.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Address2}}`	Your business address, line 2.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.City}}`	Your business city.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Locality}}`	Your business state, province, or region.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Postal}}`	Your business postal or ZIP code.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Country}}`	Your business country code, such as US.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Phone}}`	Your business phone number.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.Website}}`	Your business website.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Meeting SMS · Agreement emails
`{{Account.CountryName}}`	Your business country written out, such as United States.	Invoice layouts · Agreement documents · Agreement emails
`{{Account.Timezone}}`	Your workspace’s timezone, such as America/New_York.	Email · Workflows · Project templates · Meeting SMS
`{{AccountInfo}}`	A combined block of your business name, address, phone, and website, with line breaks.	Email · Workflows · Project templates · Legacy proposals · Meeting SMS

Client or prospect

The flow needs a specific client or prospect. An invoice or agreement can use the client details saved with that document.

Token	Populated value	Tags
`{{Client.Name}}`	The client or prospect’s name.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Address1}}`	Their address, line 1.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Address2}}`	Their address, line 2.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.City}}`	Their city.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Locality}}`	Their state, province, or region.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Postal}}`	Their postal or ZIP code.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Country}}`	Their country code.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Phone}}`	Their phone number.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Website}}`	Their website.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Initials}}`	The client’s initials used by Moxie.	Email · Workflows · Project templates · Agreement documents · Portal pages · Tickets · Meeting SMS · Agreement emails
`{{Client.Id}}`	The client record’s unique ID.	Email · Workflows · Project templates · Meeting SMS
`{{Client.RecordType}}`	Whether the record is a client or prospect.	Email · Workflows · Project templates · Portal pages · Meeting SMS
`{{Client.TaxId}}`	The client’s tax ID.	Invoice layouts · Agreement documents · Portal pages · Legacy proposals · Agreement emails
`{{Client.CountryName}}`	The client’s country written out.	Invoice layouts · Agreement documents · Agreement emails
`{{Client.DepositBalance}}`	The client deposit balance supplied with this invoice, formatted as money.	Invoice layouts
`{{Client.HourlyRate}}`	The client’s hourly rate, formatted in the agreement’s currency.	Agreement documents · Agreement emails
`{{Client.TaxRate}}`	The tax rate used by the agreement.	Agreement documents · Agreement emails
`{{Client.Color}}`	The client’s saved brand color.	Portal pages
`{{Client.Logo}}`	The URL of the client’s logo. Use as an image source where supported.	Portal pages
`{{ClientInfo}}`	A combined block of client name, address, phone, and website, with line breaks.	Email · Workflows · Project templates · Tickets · Legacy proposals · Meeting SMS

Contacts

Contact means the person supplied by the flow. In a regular email, this can be the selected contact or contacts; a client’s primary contact can be the fallback. In a bulk email, it is the individual recipient. In an agreement send email, the name and email tokens refer to that email’s signer. In an invoice layout, it is the invoice’s saved contact. On a portal page, it is the signed-in contact. Multiple contacts can be joined with “ & ” in flows that supply a list.

Token	Populated value	Tags
`{{Contact.First}}`	The contact’s first name.	Email · Workflows · Project templates · Invoice layouts · Agreement emails · Portal pages · Tickets · Meeting SMS
`{{Contact.Last}}`	The contact’s last name.	Email · Workflows · Project templates · Invoice layouts · Agreement emails · Portal pages · Tickets · Meeting SMS
`{{Contact.FullName}}`	The contact’s first and last name.	Email · Workflows · Project templates · Invoice layouts · Agreement emails · Portal pages · Tickets · Meeting SMS
`{{Contact.Email}}`	The contact’s email address.	Email · Workflows · Project templates · Invoice layouts · Agreement emails · Portal pages · Tickets · Meeting SMS
`{{Contact.Phone}}`	The contact’s phone number.	Email · Workflows · Project templates · Invoice layouts · Portal pages · Tickets · Meeting SMS
`{{Contact.Mobile}}`	The signed-in contact’s mobile number.	Portal pages
`{{Contact.Role}}`	The contact’s role or job title.	Portal pages · Legacy proposals
`{{Contact.Default.First}}`	The first name of the client’s first contact marked as a primary contact.	Email · Workflows · Project templates · Agreement emails · Meeting SMS
`{{Contact.Default.Last}}`	The last name of the client’s first contact marked as a primary contact.	Email · Workflows · Project templates · Agreement emails · Meeting SMS
`{{Contact.Default.FullName}}`	The full name of the client’s first contact marked as a primary contact.	Email · Workflows · Project templates · Agreement emails · Meeting SMS
`{{Contact.Default.Email}}`	The email address of the client’s first contact marked as a primary contact.	Email · Workflows · Project templates · Agreement emails · Meeting SMS
`{{Contact.Default.Phone}}`	The phone number of the client’s first contact marked as a primary contact.	Email · Workflows · Project templates · Agreement emails · Meeting SMS
`{{Contact.Invoice.First}}`	The first name of the client’s first contact marked as an invoice contact.	Email · Workflows · Project templates · Meeting SMS
`{{Contact.Invoice.Last}}`	The last name of the client’s first contact marked as an invoice contact.	Email · Workflows · Project templates · Meeting SMS
`{{Contact.Invoice.FullName}}`	The full name of the client’s first contact marked as an invoice contact.	Email · Workflows · Project templates · Meeting SMS
`{{Contact.Invoice.Email}}`	The email address of the client’s first contact marked as an invoice contact.	Email · Workflows · Project templates · Meeting SMS
`{{Contact.Invoice.Phone}}`	The phone number of the client’s first contact marked as an invoice contact.	Email · Workflows · Project templates · Meeting SMS

Contact lists

These tokens produce comma-separated lists. They are especially useful in workflow recipient fields. They need a client and its contact list. Phone lists currently include contacts with a saved email address, so a phone-only contact may not appear.

Token	Populated value	Tags
`{{Contacts.Default}}`	Email addresses for the client’s contacts marked as primary contacts.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.Phone.Default}}`	Phone numbers for the client’s contacts marked as primary contacts.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.All}}`	Email addresses for the client’s all contacts with an email address.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.Phone.All}}`	Phone numbers for the client’s all contacts with an email address.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.Invoice}}`	Email addresses for the client’s contacts marked as invoice contacts.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.Phone.Invoice}}`	Phone numbers for the client’s contacts marked as invoice contacts.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.Portal}}`	Email addresses for the client’s contacts with portal access.	Email · Workflows · Project templates · Meeting SMS
`{{Contacts.Phone.Portal}}`	Phone numbers for the client’s contacts with portal access.	Email · Workflows · Project templates · Meeting SMS

Opportunities

These tokens need a particular sales opportunity. Agreement documents can use the linked opportunity’s name, description, person, business, address, and custom-field details. Pipeline status and value tokens need the opportunity context supplied to an email or workflow.

Token	Populated value	Tags
`{{Opportunity.Id}}`	The opportunity’s unique ID.	Email · Workflows
`{{Opportunity.Stage}}`	The opportunity’s pipeline stage label.	Email · Workflows
`{{Opportunity.Sentiment}}`	The opportunity’s confidence or sentiment value.	Email · Workflows
`{{Opportunity.Value}}`	The opportunity value as a number; 0 if no value is saved.	Email · Workflows
`{{Opportunity.EstCloseDate}}`	The estimated closing date, formatted for display.	Email · Workflows
`{{Opportunity.ActualCloseDate}}`	The actual closing date, formatted for display.	Email · Workflows
`{{Opportunity.EstCloseDate.ISO}}`	The estimated closing date as YYYY-MM-DD.	Email · Workflows
`{{Opportunity.ActualCloseDate.ISO}}`	The actual closing date as YYYY-MM-DD.	Email · Workflows
`{{Opportunity.TaxId}}`	The tax ID stored in the opportunity’s captured form details.	Email · Workflows
`{{Opportunity.Name}}`	The opportunity’s name.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.FirstName}}`	The first name in the opportunity’s captured contact details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.LastName}}`	The last name in those contact details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.FullName}}`	The full name in those contact details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Email}}`	The email address in those contact details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Phone}}`	The phone number in those contact details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.BusinessName}}`	The business name in the opportunity’s captured details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Website}}`	The website in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Address1}}`	The address, line 1, in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Address2}}`	The address, line 2, in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.City}}`	The city in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Locality}}`	The state, province, or region in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Postal}}`	The postal or ZIP code in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Country}}`	The country code in those details.	Email · Workflows · Agreement documents · Agreement emails
`{{Opportunity.Description}}`	The opportunity’s description.	Agreement documents · Agreement emails
`{{Opportunity.Role}}`	The role or job title in the opportunity’s captured contact details.	Agreement documents · Agreement emails
`{{Opportunity.CountryName}}`	The country in those details, written out.	Agreement documents · Agreement emails

Invoices

An invoice flow needs a specific invoice. Invoice layouts are the invoice document itself; invoice emails and workflows have a different set of available fields. A recurring-invoice or payment-plan preview can show placeholders until the actual invoice is created.

Token	Populated value	Tags
`{{Invoice.Number}}`	The formatted invoice number.	Email · Workflows · Invoice layouts
`{{Invoice.Status}}`	The invoice’s status.	Email · Workflows · Invoice layouts
`{{Invoice.PurchaseOrder}}`	The purchase order reference.	Email · Workflows · Invoice layouts
`{{Invoice.DateDue}}`	The payment due date, formatted for display.	Email · Workflows · Invoice layouts
`{{Invoice.OnlineUrl}}`	The link to view this invoice online.	Email · Workflows · Invoice layouts
`{{Invoice.PayUrl}}`	The link to pay this invoice.	Email · Workflows · Invoice layouts
`{{Invoice.Currency}}`	The invoice currency code, such as USD.	Email · Workflows · Invoice layouts
`{{Invoice.Total}}`	The invoice total, formatted as money.	Email · Workflows · Invoice layouts
`{{Invoice.AmountDue}}`	The remaining amount due, formatted as money.	Email · Workflows · Invoice layouts
`{{Invoice.Id}}`	The invoice’s unique ID.	Email · Workflows
`{{Invoice.Description}}`	The invoice’s description.	Email · Workflows
`{{Invoice.DateSent}}`	The invoice’s sent/issued date, formatted for display.	Email · Workflows
`{{Invoice.DateSent.ISO}}`	The sent/issued date as YYYY-MM-DD.	Email · Workflows
`{{Invoice.DateDue.ISO}}`	The due date as YYYY-MM-DD.	Email · Workflows
`{{Invoice.DaysPastDue}}`	The invoice’s calculated number of days past due.	Email · Workflows
`{{Invoice.DaysUntilDue}}`	The invoice’s calculated number of days until due.	Email · Workflows
`{{Invoice.PaymentTotal}}`	The total payments recorded on this invoice, formatted as money.	Email · Workflows
`{{Invoice.PaymentMethod}}`	The invoice’s automatic-payment method, when one is set.	Email · Workflows
`{{Invoice.LateFee}}`	In invoice emails/workflows: the calculated plus applied late-fee amount, formatted as money. In invoice layouts: the monthly late-fee percentage from the payment terms.	Email · Workflows · Invoice layouts
`{{Invoice.DateCreated}}`	The invoice’s creation date, in long date format.	Invoice layouts
`{{Invoice.DateIssued}}`	The invoice’s sent/issued date, in long date format.	Invoice layouts
`{{Invoice.PayInstructions}}`	The invoice’s payment instructions, with line breaks.	Invoice layouts
`{{Invoice.ComplianceHeader}}`	The invoice document heading from invoice preferences; the paid heading is used for a paid invoice.	Invoice layouts

Invoice payments and subscription requests

Payment details need an actual payment, not just an invoice. Subscription tokens belong to the subscription checkout-request email. Booking pages also use Payment.Amount, with the different meaning shown below.

Token	Populated value	Tags
`{{Payment.Id}}`	The payment’s unique ID.	Payment emails · Workflows
`{{Payment.DatePaid}}`	The date the payment was made.	Payment emails · Workflows
`{{Payment.Currency}}`	The payment currency code.	Payment emails · Workflows
`{{Payment.Provider}}`	The payment provider.	Payment emails · Workflows
`{{Payment.PaidBy}}`	The saved name or description of who paid.	Payment emails · Workflows
`{{Payment.Memo}}`	The payment memo.	Payment emails · Workflows
`{{Payment.Amount}}`	In a payment email/workflow: the recorded payment amount. On a booking page: the required booking payment amount. Formatted as money.	Payment emails · Workflows · Booking pages
`{{Subscription.Link}}`	The checkout link for this subscription request.	Subscription emails
`{{Subscription.ProductSelection}}`	A formatted summary of the products selected for the subscription request.	Subscription emails

Agreements and signers

These tokens need a specific agreement. A signing link belongs in the send email. The document can show a signing-date preview before signing; it is not proof that the agreement has already been signed. Use the status tokens in a workflow when you need to check completion.

Token	Populated value	Tags
`{{Agreement.Name}}`	The agreement’s name.	Email · Workflows · Agreement documents · Agreement emails
`{{Agreement.DateCreated}}`	The agreement’s creation date.	Email · Workflows · Agreement documents · Agreement emails
`{{Agreement.DateSigned}}`	The completed signing date. An unsigned document preview may show today’s date.	Email · Workflows · Agreement documents · Agreement emails
`{{Agreement.ExpirationDate}}`	The agreement’s expiration date, when set. Document previews may show [Exp Date] before it is set.	Email · Workflows · Agreement documents · Agreement emails
`{{Agreement.Id}}`	The agreement’s unique ID.	Email · Workflows
`{{Agreement.DateSent}}`	The agreement’s finalized/sent date.	Email · Workflows
`{{Agreement.DateCreated.ISO}}`	The saved creation date/time in ISO format.	Email · Workflows
`{{Agreement.DateSent.ISO}}`	The saved finalized/sent date/time in ISO format.	Email · Workflows
`{{Agreement.DateSigned.ISO}}`	The saved completed signing date/time in ISO format.	Email · Workflows
`{{Agreement.FullyExecuted}}`	Yes if fully executed; otherwise No.	Email · Workflows
`{{Agreement.ClientSigned}}`	Yes if the client has signed; otherwise No.	Email · Workflows
`{{Agreement.Status}}`	Fully Executed when complete; otherwise the agreement’s status label.	Email · Workflows
`{{Agreement.OnlineUrl}}`	The online agreement link. Agreement send emails receive the personal link for that signer.	Agreement emails · Workflows
`{{Agreement.DateCreatedFull}}`	The creation date in long form.	Agreement documents · Agreement emails
`{{Agreement.DateSignedFull}}`	The completed signing date and time in long form; an unsigned preview may show today’s date.	Agreement documents · Agreement emails
`{{Agreement.ExpirationDateFull}}`	The expiration date in long form, or [Exp Date] in an unset document preview.	Agreement documents · Agreement emails
`{{Agreement.TaxDetails}}`	A description of the taxes applied to the agreement.	Agreement documents · Agreement emails
`{{Signer.FirstName}}`	The client signer’s first name; in a send email, that email’s signer.	Email · Workflows · Agreement documents · Agreement emails
`{{Signer.LastName}}`	The client signer’s last name; in a send email, that email’s signer.	Email · Workflows · Agreement documents · Agreement emails
`{{Signer.Email}}`	The client signer’s email address; in a send email, that email’s signer.	Email · Workflows · Agreement documents · Agreement emails
`{{Signer.Title}}`	The client signer’s title; in a send email, that email’s signer.	Email · Workflows · Agreement documents · Agreement emails

Agreement totals

These values are calculated from the agreement’s pricing and customer selections. An amount may change when a customer changes a package, add-on, or payment choice. Availability in a document or pricing-aware preview does not make these general-purpose workflow-email tokens. Recurring totals add the selected recurring schedules together; if the schedules have different billing periods, the sum is not a single monthly charge.

Token	Populated value	Tags
`{{UpFront.Total}}`	The amount due up front, including tax, before card processing fees.	Agreement pricing
`{{UpFront.UnformattedTotal}}`	The same up-front total as a plain number, without currency formatting.	Agreement pricing
`{{UpFront.TotalWithoutTax}}`	The amount due up front before tax.	Agreement pricing
`{{UpFront.Tax}}`	The tax included in the up-front amount.	Agreement pricing
`{{UpFront.CardProcessingFees}}`	The card processing fee on the up-front amount.	Agreement pricing
`{{UpFront.UnformattedCardProcessingFees}}`	The up-front card processing fee as a plain number.	Package offers
`{{UpFront.TotalWithCardProcessingFees}}`	The amount due up front including tax and card processing fees.	Package offers
`{{UpFront.UnformattedTotalWithCardProcessingFees}}`	The same total including card processing fees as a plain number.	Package offers
`{{OneTime.Total}}`	The one-time subtotal before tax. The included charges follow the agreement’s pricing setup.	Agreement pricing
`{{OneTime.TotalWithTax}}`	The one-time total including tax.	Agreement pricing
`{{OneTime.Tax}}`	The tax on the one-time charges.	Agreement pricing
`{{Recurring.Total}}`	The combined recurring subtotal before tax.	Agreement pricing
`{{Recurring.TotalWithTax}}`	The combined recurring total including tax.	Agreement pricing
`{{Recurring.Tax}}`	The combined tax on recurring charges.	Agreement pricing
`{{PackageOffer.Total}}`	The selected payment choice’s total including tax.	Package offers
`{{PackageOffer.TotalWithoutTax}}`	The selected payment choice’s subtotal after discounts, before tax.	Package offers
`{{PackageOffer.OriginalTotalWithoutTax}}`	The selected payment choice’s subtotal before discounts and tax.	Package offers
`{{PackageOffer.Tax}}`	The selected payment choice’s tax.	Package offers
`{{PackageOffer.Discount}}`	The discount amount recorded on the one-time portion of the quote.	Package offers
`{{PackageOffer.UpFrontTotal}}`	The amount due up front, including tax, before card processing fees.	Package offers
`{{PackageOffer.PaymentChoice}}`	The label of the selected payment choice.	Package offers
`{{PackageOffer.Currency}}`	The quote’s currency code.	Package offers

Individual service packages

Package tokens describe the particular service package being rendered. Use them inside that package’s description. A general agreement text block does not automatically know which package you mean. These tokens belong to Services packages; PackageOffer tokens above describe the newer package-offer quote.

Token	Populated value	Tags
`{{Package.Name}}`	This package’s name.	Service package descriptions
`{{Package.Total}}`	This package’s displayed price before tax; for hourly pricing, this can be its hourly rate.	Service package descriptions
`{{Package.TotalWithTax}}`	This package’s displayed price including tax.	Service package descriptions
`{{Package.Tax}}`	The tax on this package’s displayed price.	Service package descriptions
`{{Package.TaxRate}}`	The tax rate for this package.	Service package descriptions
`{{Package.FeeLabel}}`	The pricing label, such as Fixed Price, Hourly, or the recurring billing period.	Service package descriptions
`{{Package.StartDate}}`	The package’s start date; -- if none is set.	Service package descriptions
`{{Package.HourEstimateMin}}`	The minimum estimated hours.	Service package descriptions
`{{Package.HourEstimateMax}}`	The maximum estimated hours.	Service package descriptions
`{{Package.DepositPercent}}`	The deposit percentage for hourly or per-item pricing; N/A when not applicable.	Service package descriptions
`{{Package.DepositAmount}}`	The calculated deposit amount.	Service package descriptions
`{{Package.HourlyOverage}}`	The hourly rate for work beyond the retainer allowance.	Service package descriptions

Individual service items

Item tokens need the particular line item inside an agreement’s Services package. Use them in that item’s supported text; they are not general invoice-line or project-task tokens.

Token	Populated value	Tags
`{{Item.Product}}`	The selected product or service name.	Service item descriptions
`{{Item.Quantity}}`	The item quantity.	Service item descriptions
`{{Item.Rate}}`	The item rate, formatted as money when set.	Service item descriptions
`{{Item.Total}}`	The item’s quantity × rate, before tax.	Service item descriptions
`{{Item.DueDate}}`	The item’s due-date text, including its configured relative-date wording when applicable.	Service item descriptions
`{{Item.TaxLabel}}`	The agreement’s tax label, such as Tax.	Service item descriptions
`{{Item.TaxRate}}`	The applicable tax percentage, or 0% for a non-taxable item.	Service item descriptions
`{{Item.TaxDetails}}`	The applicable tax description, or a zero-tax description for a non-taxable item.	Service item descriptions
`{{Item.Tax}}`	The tax amount on this item.	Service item descriptions
`{{Item.TotalWithTax}}`	The item total including tax.	Service item descriptions

Projects and tasks

These describe an existing project or task supplied to an email or workflow. They are not the shared tokens offered when creating a project from a project template. Project templates instead use the business, client, contact, date/time, and link tokens tagged Project templates.

Token	Populated value	Tags
`{{Project.Id}}`	The project’s unique ID.	Email · Workflows
`{{Project.Name}}`	The project’s name.	Email · Workflows
`{{Project.StartDate}}`	The project’s start date, formatted for display.	Email · Workflows
`{{Project.DueDate}}`	The project’s due date, formatted for display.	Email · Workflows
`{{Project.StartDate.ISO}}`	The project’s start date as YYYY-MM-DD.	Email · Workflows
`{{Project.DueDate.ISO}}`	The project’s due date as YYYY-MM-DD.	Email · Workflows
`{{Task.Id}}`	The task’s unique ID.	Email · Workflows
`{{Task.Name}}`	The task’s name.	Email · Workflows
`{{Task.StartDate}}`	The task’s start date, formatted for display.	Email · Workflows
`{{Task.DueDate}}`	The task’s due date, formatted for display.	Email · Workflows
`{{Task.StartDate.ISO}}`	The task’s start date as YYYY-MM-DD.	Email · Workflows
`{{Task.DueDate.ISO}}`	The task’s due date as YYYY-MM-DD.	Email · Workflows
`{{Project.Complete}}`	No for an active project; Yes for a project that is not active.	Email · Workflows
`{{Task.Status}}`	The task’s status label; Unknown if its status cannot be matched.	Email · Workflows
`{{Task.LastComment}}`	The task’s latest non-private comment, or the triggering comment in a comment notification.	Email · Workflows · Task notifications
`{{Task.LastCommentBy}}`	The saved author of the task’s latest non-private comment.	Email · Workflows · Task notifications

Scheduled meetings

These tokens need a booked meeting. A scheduler is the page people use to book; a scheduled meeting is the appointment they booked. The page can exist before an appointment, attendee, or payment exists. Times below use the booked meeting’s timezone.

Token	Populated value	Tags
`{{Meeting.Id}}`	The booked meeting’s unique ID.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.SchedulerName}}`	The name of the scheduler used to book.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.Name}}`	The booked meeting’s name. On a booking page, this means the scheduler’s name.	Meeting emails · Workflows · Booking pages · Meeting SMS
`{{Meeting.Location}}`	The booked meeting’s location description. On a booking page, this is the selected location type or short label.	Meeting emails · Workflows · Booking pages · Meeting SMS
`{{Meeting.Start}}`	The appointment’s start date and time in the standard display format.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.StartFull}}`	The appointment’s start date and time in the longer display format.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.End}}`	The appointment’s end date and time in the standard display format.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.EndFull}}`	The appointment’s end date and time in the longer display format.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.Start.ISO}}`	The saved start date/time in ISO format, including timezone information.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.End.ISO}}`	The saved end date/time in ISO format, including timezone information.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.Duration}}`	For a booked meeting, its duration in minutes. On a booking page, the configured duration number; pair with Meeting.TimeUnit.	Meeting emails · Workflows · Booking pages · Meeting SMS
`{{Meeting.Timezone}}`	The booked meeting’s timezone. The spelling uses a lowercase z.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.FirstName}}`	The attendee’s first name from the booking details.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.LastName}}`	The attendee’s last name from the booking details.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.FullName}}`	The attendee’s full name.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.Email}}`	The attendee’s email address.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.Phone}}`	The attendee’s phone number.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.CancelUrl}}`	The link for cancelling this appointment.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.ChangeUrl}}`	The link for rescheduling this appointment.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.PaymentAmount}}`	The amount of the recorded booking payment, formatted as money.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.PaymentMethod}}`	The source or method of the recorded booking payment.	Meeting emails · Workflows · Meeting SMS
`{{Meeting.PaymentReceipt}}`	The receipt URL for the recorded booking payment.	Meeting emails · Workflows · Meeting SMS

Booking-page text and icons

These tokens belong to the scheduler’s public booking screens. A selected time or location is needed for the matching value. Icon tokens insert a small inline icon in supported booking-page content. They do not insert an icon into an ordinary email or text message.

Token	Populated value	Tags
`{{Meeting.TimeUnit}}`	The unit for the configured duration, such as Minutes or Hours. Use with Meeting.Duration.	Booking pages
`{{Meeting.ScheduledTime}}`	The selected/confirmed appointment time as displayed on the booking page.	Booking pages
`{{Meeting.AccountName}}`	The host business’s name.	Booking pages
`{{Meeting.OwnerName}}`	The scheduler owner’s name.	Booking pages
`{{Meeting.LocationInfo}}`	The full description or details of the selected meeting location.	Booking pages
`{{Meeting.TimeZone}}`	The timezone currently used on the booking page. The spelling uses a capital Z.	Booking pages
`{{Meeting.Description}}`	The scheduler’s description.	Booking pages
`{{Icons.Clock}}`	A clock icon.	Booking pages
`{{Icons.Event}}`	A calendar/event icon.	Booking pages
`{{Icons.Public}}`	A globe icon.	Booking pages
`{{Icons.Info}}`	An information icon.	Booking pages
`{{Icons.Mic}}`	A microphone icon.	Booking pages

Forms and form requests

Form tokens describe answers that have already been submitted. They can also come from booking-form answers or opportunity form details when a flow supplies those. FormRequest tokens describe a particular request to complete a form. Forms.<form-id>, in the links section, is a reusable public form link.

Token	Populated value	Tags
`{{Form.Name}}`	The submitted form’s name. A flow using captured opportunity details may use the opportunity name.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.FirstName}}`	The first name in the submitted details.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.LastName}}`	The last name in the submitted details.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.FullName}}`	The full name in the submitted details.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Email}}`	The submitted email address.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Phone}}`	The submitted phone number.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.BusinessName}}`	The submitted business name.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Website}}`	The submitted website.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Address1}}`	The submitted address, line 1.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Address2}}`	The submitted address, line 2.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.City}}`	The submitted city.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Locality}}`	The submitted state, province, or region.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Postal}}`	The submitted postal or ZIP code.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.Country}}`	The submitted country code.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.TaxId}}`	The submitted tax ID.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.SourceUrl}}`	The saved source URL for the submission.	Form follow-ups · Email · Workflows · Meeting SMS
`{{Form.SubmissionUrl}}`	The link to this submission, when a submission link is available.	Form follow-ups · Email · Workflows · Meeting SMS
`{{FormRequest.Name}}`	The name of the form request.	Form requests · Email · Workflows
`{{FormRequest.OnlineUrl}}`	The link for completing that specific form request.	Form requests · Email · Workflows

Tickets and ticket replies

These tokens need the ticket being handled. Reply tokens also need a particular reply/comment. A ticket template does not automatically get every token available to a regular email template.

Token	Populated value	Tags
`{{Ticket.Number}}`	The ticket number.	Tickets · Ticket emails
`{{Ticket.Subject}}`	The ticket subject.	Tickets · Ticket emails
`{{Ticket.Status}}`	The ticket’s status value.	Tickets · Ticket emails
`{{Ticket.Type}}`	The ticket type’s name.	Tickets · Ticket emails
`{{Ticket.PortalUrl}}`	For a client notification: the ticket’s portal link. For an internal notification: the ticket’s link in Moxie.	Tickets · Ticket emails
`{{Ticket.CompletionPolicy}}`	The completion-policy value saved on the ticket type.	Tickets · Ticket emails
`{{Ticket.Reply.AuthorName}}`	The reply author’s name.	Tickets · Ticket emails
`{{Ticket.Reply.AuthorEmail}}`	The reply author’s email address.	Tickets · Ticket emails
`{{Ticket.Reply.Content}}`	The reply/comment content.	Tickets · Ticket emails

Reusable links and email signatures

Choose a scheduler or form from the token picker to insert its exact token. A token’s ID is not its display name. A booking or form link can carry the current opportunity along when generated from an opportunity flow.

Token	Populated value	Tags
`{{Scheduler.<scheduler-id>}}`	The public booking URL for that scheduler.	Email · Workflows · Project templates · Meeting SMS
`{{Forms.<form-id>}}`	The public URL for that form.	Email · Workflows · Project templates · Meeting SMS
`{{Portal.Url}}`	Your client portal link. Some task notifications supply a more specific portal destination.	Email · Workflows · Project templates · Tickets · Task notifications · Meeting SMS
`{{Email.Signature}}`	The signature for the sending mailbox or automated sender used by the flow. Without a selected mailbox, the automated email signature may be used.	Email · Workflows · Project templates · Agreement emails · Tickets · Meeting SMS

Current date and time

These values are filled when the flow replaces the tokens, using the workspace timezone. They are not the date the template was written. Examples below use September 15, 2026 at 14:30; month names can follow the applicable language settings.

Token	Populated value	Tags
`{{Date.MMDDYYYY}}`	The current date as 09/15/2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.MMMDDYYYY}}`	The current date as Sep 15, 2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.MMMMDDYYYY}}`	The current date as September 15, 2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.DDMMYYYY}}`	The current date as 15/09/2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.DDMMMYYYY}}`	The current date as 15 Sep 2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.DDMMMMYYYY}}`	The current date as 15 September 2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.YYYYMMDD}}`	The current date as 2026-09-15.	Email · Workflows · Project templates · Meeting SMS
`{{Date.Month}}`	The current month name, such as September.	Email · Workflows · Project templates · Meeting SMS
`{{Date.Year}}`	The current four-digit year, such as 2026.	Email · Workflows · Project templates · Meeting SMS
`{{Date.24HR}}`	The current time in 24-hour format, such as 14:30.	Email · Workflows · Project templates · Meeting SMS
`{{Date.12HR}}`	The current time in 12-hour format, such as 2:30 PM.	Email · Workflows · Project templates · Meeting SMS
`{{Time.24HR}}`	The current time in 24-hour format; an alternative to Date.24HR.	Email · Workflows · Project templates · Meeting SMS
`{{Time.12HR}}`	The current time in 12-hour format; an alternative to Date.12HR.	Email · Workflows · Project templates · Meeting SMS

Custom fields and individual form answers

These are token patterns, because each workspace has its own fields. Replace <field-key> with the field’s exact mapping key, preferably by choosing the field in the token picker. For example, a client field whose key is weddingDate uses {{Client.Custom.weddingDate}}. The angle-bracket text is an instruction, not part of the real token. Date fields can have an .ISO version that returns the saved date, usually YYYY-MM-DD. The .ISO version needs a saved date and is not supported on every document surface.

Token	Populated value	Tags
`{{Client.Custom.<field-key>}}`	The value of that custom field on the client. Date values are formatted for display.	Email · Workflows · Project templates · Invoice layouts · Agreement documents · Portal pages · Meeting SMS
`{{Client.Custom.<field-key>.ISO}}`	The saved date for that client custom field, without display formatting.	Email · Workflows · Project templates · Portal pages · Meeting SMS
`{{Contact.Custom.<field-key>}}`	The value of that contact custom field. Multiple supplied contacts may have values joined with “ & ”.	Email · Workflows · Project templates · Invoice layouts · Portal pages · Meeting SMS
`{{Contact.Custom.<field-key>.ISO}}`	The saved date for that contact custom field. In email/workflow flows, this is supplied through the client’s primary-contact context; do not assume it follows an overridden recipient.	Email · Workflows · Project templates · Portal pages · Meeting SMS
`{{Contact.Invoice.Custom.<field-key>}}`	The custom-field value on the client’s first invoice contact.	Email · Workflows · Project templates · Meeting SMS
`{{Contact.Invoice.Custom.<field-key>.ISO}}`	The saved date for a custom field on the client’s first invoice contact.	Email · Workflows · Project templates · Meeting SMS
`{{Opportunity.Custom.<field-key>}}`	The custom-field value on the opportunity.	Email · Workflows · Agreement documents
`{{Opportunity.Custom.<field-key>.ISO}}`	The saved date for that opportunity custom field.	Email · Workflows
`{{Project.Custom.<field-key>}}`	The custom-field value on the existing project. Uses fields for its project type.	Email · Workflows
`{{Project.Custom.<field-key>.ISO}}`	The saved date for that project custom field.	Email · Workflows
`{{Task.Custom.<field-key>}}`	The custom-field value on the task. Uses fields for its project type.	Email · Workflows
`{{Task.Custom.<field-key>.ISO}}`	The saved date for that task custom field.	Email · Workflows
`{{Form.Answer.<field-key>}}`	The answer to the form question with that field key. Date-like answers are formatted for display.	Form follow-ups · Email · Workflows · Meeting SMS

Workflow reply information

These values come from email/message steps in the current opportunity’s workflow. They need the relevant thread and recorded reply. Replace <template-name> with the exact email template name; keep the lowercase .subject and .body endings.

Token	Populated value	Tags
`{{Email.<template-name>}}`	The word replied when that email step has a recorded reply.	Workflows
`{{Email.<template-name>.subject}}`	The subject saved on that replied-to workflow email thread.	Workflows
`{{Email.<template-name>.body}}`	The body saved on that replied-to workflow email thread.	Workflows
`{{Message.Reply}}`	The message text supplied by a workflow message thread.	Workflows

Legacy proposals

These tokens support older proposal flows. Proposal tokens need a particular legacy proposal; they are separate from Agreement tokens. Use the current editor’s picker for new content.

Token	Populated value	Tags
`{{Proposal.Id}}`	The legacy proposal’s unique ID.	Legacy proposals · Email · Workflows
`{{Proposal.Name}}`	The heading on its cover page.	Legacy proposals · Email · Workflows
`{{Proposal.DateSent}}`	Its sent date.	Legacy proposals · Email · Workflows
`{{Proposal.DateSigned}}`	Its signed date.	Legacy proposals · Email · Workflows
`{{Proposal.OnlineUrl}}`	The online proposal link, when available.	Legacy proposals · Email · Workflows
`{{Proposal.Status}}`	Its status label.	Legacy proposals · Email · Workflows
`{{Proposal.TotalValue}}`	The total value calculated from its selected proposal deliverables, as a plain number.	Legacy proposals · Email · Workflows
`{{Proposal.SelectedPackage}}`	The selected proposal deliverable/package names, separated by commas.	Legacy proposals · Email · Workflows
`{{ClientName}}`	The client’s name.	Legacy proposals
`{{ClientCountry}}`	The client’s country code.	Legacy proposals
`{{ClientLocality}}`	The client’s state, province, or region.	Legacy proposals
`{{ClientCurrency}}`	The client’s currency code.	Legacy proposals
`{{Client.Currency}}`	The client’s currency code.	Legacy proposals
`{{ClientLegalName}}`	The client’s saved name.	Legacy proposals
`{{ClientEntityType}}`	The legacy value Corporation; this is not looked up from a legal-entity field.	Legacy proposals
`{{Contact.FirstName}}`	The primary contact’s first name. This spelling is specific to legacy proposals.	Legacy proposals
`{{Contact.LastName}}`	The primary contact’s last name. This spelling is specific to legacy proposals.	Legacy proposals
`{{MyBusinessName}}`	Your business name.	Legacy proposals
`{{MyFirstName}}`	The creating user’s first name, when a user is available.	Legacy proposals
`{{MyLastName}}`	The creating user’s last name, when a user is available.	Legacy proposals
`{{MyName}}`	The creating user’s full name, when a user is available.	Legacy proposals
`{{MyEmail}}`	The creating user’s email address, when a user is available.	Legacy proposals
`{{<field-key>}}`	A legacy client or primary-contact custom-field value using its bare mapping key.	Legacy proposals

Invoice-number formats

These tokens work only in the invoice-number format setting. They do not work as general email or document tokens. Date pieces use the invoice’s sent date, or the current date if it has not been sent.

Token	Populated value	Tags
`{{Num}}`	The invoice sequence number, such as 42.	Invoice numbering
`{{Num\|4}}`	The sequence number padded to at least four digits, such as 0042. Replace 4 with the supported single-digit width you need.	Invoice numbering
`{{CI}}`	The client initials used for invoice numbering.	Invoice numbering
`{{YYYY}}`	The four-digit year, such as 2026.	Invoice numbering
`{{YY}}`	The two-digit year, such as 26.	Invoice numbering
`{{Mon}}`	The three-letter month, such as Sep.	Invoice numbering
`{{MON}}`	The uppercase three-letter month, such as SEP.	Invoice numbering
`{{MM}}`	The two-digit month, such as 09.	Invoice numbering
`{{DD}}`	The two-digit day, such as 15.	Invoice numbering

Why is my token blank or still showing?

A missing value can appear as a blank, --, or the original {{Token}}, depending on the editor or flow. A template preview may also use sample information. Seeing a sample value does not mean a real record is already connected.

Check the spelling. Copy the exact token from this article or the picker.
Check the tags. A booking-page token will not automatically work in an invoice email.
Check the record. Does this step have the actual invoice, meeting, agreement, contact, or other record it needs?
Check the field. A client with no phone number cannot supply a phone-number value.
Preview or test the actual flow with the intended records before sending it to customers.

For example, if “Your invoice {{Invoice.Number}} is ready” has no invoice number, connect or create the invoice before that message runs. Typing the token again will not give the flow the missing invoice.

Back to Settings & administration

Moxie tokens: what they fill in and where to use them