Custom and Google fonts

Landing pages, emails, and forms can use any Google Font or your own uploaded brand fonts. Every font picker offers three sources: system fonts, the full Google Fonts catalog, and the custom fonts your workspace uploads under Settings → Fonts. Pick a font in a theme or on a single block, and set the fallbacks shown wherever it can’t load.

Upload WOFF2, WOFF, TTF, or OTF files up to 4 MB each, one per weight and style or a single variable font, and Conversion reads each file’s weight and style. Gmail and Outlook don’t load web fonts, so email font selects flag Google and custom fonts, and the email toolbar can preview the canvas with fallbacks only, the way those clients render it.

Luma registration questions

Answers to Luma registration forms can fill contact, company, and campaign member fields. Choose Manage fields on the Luma row in Settings → Integrations to see every question, including your own, which appear as soon as a field event is connected to a Luma event. Map a question to as many fields as you like, and choose whether its answers fill only empty values or replace existing ones. Company, Job Title, and Phone Number come mapped by default.

Asana triggers for custom agents

Custom agents can start from Asana. A trigger fires when a task is added, updated, commented on, moved to a section, or assigned to the agent, and can be filtered by project, section, tag, assignee, or completion. Each task gets one agent session, and a new task waits until edits settle so the agent starts on the filled-in version.

The agent can read the task with its custom fields and attachments, comment on it, complete it, or move it to another section. It only writes to the task that triggered it.

Landing page layout and form scripts

Rows have a Stretch option for vertical alignment, so cards in a row match the tallest one’s height. Forms on landing pages accept the same set-values and submitted messages as embedded forms, so a script on the page can prefill fields or react to a submission without an iframe. The submitted message now carries the form’s ID.

Improvements

• Agents Agents can search your earlier chats, so a new chat can pick up a reference like the email you drafted last week. Each person’s agent only sees their own chats.
• Agents Agents can email workspace members, such as an alert to a rep. Messages are plain text from a no-reply address, and the tool asks for approval by default.
• Agents Agents can change Salesforce field sync settings for up to 100 fields at once, after your approval.
• Email The section Mobile layout setting offers Side by side, Stack, and Stack in reverse, so text can sit above its image on phones.
• Email Tab accepts autocomplete suggestions and indents in the Liquid, HTML, and SQL editors, and Shift-Tab outdents.
• Data Model Contact warehouse syncs can write company fields when a column is aliased as __company__<field_key>.
• API Public API requests can pass the API key in an api_key query parameter for tools that can’t set headers. The X-API-Key header is still preferred.
• API MCP clients can upload images, files, and contact CSVs from a public HTTPS URL.

Fixes

• CRM Sync Failed Salesforce sync jobs retry automatically, and a permission error on one object no longer holds up objects that don’t depend on it.
• Admin Editors and Viewers can open campaign pages and use integration pickers, such as Slack channels and Salesforce campaigns, without an access error.
• Email Changing the subscription status of every contact that matches a filter runs as a background action, so large updates finish reliably.
• Agents The agent can build audiences that filter through linked records, such as custom objects.
• Integrations LinkedIn lead gen leads include the ad’s name, not only its ID.