Everything you need to spin up a new email builder from the template.
Collect these from the client before starting:
[[S63:3]])
Required
[[S1:first_name]]
*|FNAME|*
{{contact.firstname}}
Required
.xlsx or .csv with tracking URLs. Note the column header names they use.
Optional
_template folder._template/ → CoastGuard/coastguard-builder/
AI Email Builder/ ├── OCC/ ← existing ├── CoastGuard/ ← new client │ └── coastguard-builder/ │ ├── CLIENT_CONFIG.js │ ├── index.html │ ├── help/ │ ├── drop-google-doc-html-here/ │ └── _do-not-edit/ └── _template/ ← stays untouched
Open CLIENT_CONFIG.js and replace every CHANGE_ME value. Every field is documented with inline comments.
Upload the client’s Google Doc HTML + brand assets to Claude and say:
“Here is a new client’s email copy document and their brand info: [colors, fonts, signers, merge field syntax]. Fill in CLIENT_CONFIG.js for me.”
Claude can detect signer names, greeting patterns, language, and segment structure directly from reading the email copy.
Key sections to fill in:
orgName, orgNameFr, appTitlecolorPrimary, colorAccent, etc.fontFamilyfirstName, bodySlot, yearTokenindex.html in a text editor.<!-- PASTE YOUR CLIENT'S STATIONERY WRAPPER HTML BELOW --> <script type="text/html" id="stationery-wrapper"> ...placeholder HTML here... </script>
<script type="text/html"> and </script> with the client’s full stationery wrapper HTML.[[S63:3]]) matching what you set in CLIENT_CONFIG.mergeFields.bodySlot._do-not-edit/email-assets/stationery_wrapper.html as a backup reference.<script type="text/html"> tag (not loaded via fetch) so it works when opening index.html directly from the filesystem (file:// protocol).index.html to open it in Chrome.{need UTM} placeholders if no spreadsheet)[First Name] → platform merge code)The help page (help/index.html) ships with generic language. Optionally update: