> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/workflow-automation/merge-fields.md).

# Merge Fields

Personalising email and text content with client details — what tokens are available and how they resolve.

Any Email, Automated Email, Text Message, or Automated Text Message action can include `{{Token}}` placeholders in its content — filled in with real client details when the message actually sends (or when you use Preview with a real client).

Two tiers, both available from the **Insert merge field** menu in the action editor.

## Computed

A small set of tags that need logic beyond a plain field lookup:

| Token                                                                       | Resolves to                                                                                                                                      |
| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `{{Client Name}}` / `{{Client First Name}}`                                 |                                                                                                                                                  |
| `{{Partner Name}}`                                                          | The *other* household member — automatically found, blank if there isn't one                                                                     |
| `{{Household Name}}`                                                        |                                                                                                                                                  |
| `{{Adviser Name}}`                                                          | The Job owner                                                                                                                                    |
| `{{Job Name}}`                                                              |                                                                                                                                                  |
| `{{Due Date}}`                                                              |                                                                                                                                                  |
| `{{Calendly Link}}`                                                         | The Job owner's booking link (prefers a "Review"-type link, falls back to their default) — blank if they don't have one on file                  |
| `{{Primary Adviser Calendly Link}}` / `{{Secondary Adviser Calendly Link}}` | Same idea, but keyed off the **Account's** Owner / Secondary Adviser rather than the Job owner — useful since a Job isn't always owned by either |
| `{{Company Name}}`                                                          | Reserved, not wired to a source field yet — always renders blank                                                                                 |

A Calendly Link token inserted into an Email drops in as a real clickable "Book your appointment" link when the email actually sends — in Text Message it's just the bare URL, since there's no formatting to apply there.

## Account Fields

A live, searchable list of **every real field on the Job's linked Account** — not hardcoded, so a brand-new custom field you add to Account shows up automatically with no extra work. Includes one level of dot-walk into parent lookups, e.g. `{{Owner.Email}}`.

If you type a token that isn't a real, accessible Account field, it's left exactly as typed rather than breaking the message — easy to spot a typo, and one bad token never blanks out an otherwise-good message.

## Why Account, not the Job itself

Merge fields always resolve against the **Account**, never the Job record — that's the one thing both a real send and a zero-cost preview (no Job actually exists yet) always have in common.

## Team roles and named links

Workflow emails also understand the team-role and named-link merge fields used in client requests, such as `{{Role:Broker.FirstName}}` and `{{Role:Broker.Link:Credit Guide}}`, and the `{{#Role:…}}…{{/Role:…}}` blocks that only show when someone holds the role. They're filled in when the email sends, the same way. See [Building a Client Request Template](/workflow/client-requests/building-a-client-request-template.md#team-roles).

## See also

* Action Types Reference
* Testing & Previewing