How does the Google Docs integration work?

Write your newsletter in Google Docs and import it straight into the Letterhead composer with the Google Docs integration block.

Structure your document first

1. Use the Heading options (H1, H2, H3), or Google Docs’ own Title and Subtitle styles — Title imports as an H1 and Subtitle as an H2, the same as if you’d used the Heading options directly.
2. Use normal body text for standard paragraph content.
3. Links in your document import as URL blocks.

Import into Letterhead

1. Open your draft from Emails.
2. Scroll to the Integrations section at the very bottom of the block panel and drag the Google Docs block into the draft.
3. Click the block and choose Choose a Google Doc.
4. Log in to your Google account when prompted and grant the requested permissions.
5. Select the Google Doc to import.

How formatting maps

Google Docs	Letterhead
H1 / H2 / H3	H1 / H2 / H3
Divider	Divider
Bulleted list	Paragraph with bulleted list
Image	Image (any link on it preserved)
URLs	URL blocks

Title and Subtitle paragraph styles import too — as an H1 and H2 respectively, same as the Heading options above.

If you’ve attached a hyperlink to an image in your doc, that link comes across on import too — the image arrives as a linked image, with the URL already set on the image block, so you don’t have to add it again by hand.

Where the look comes from

Your document brings across its structure and text formatting — headings, lists, bold, italics, and links. By default, everything about how the imported blocks look comes from your own newsletter’s styles instead: fonts, text and background colours, padding, and borders. So an import lands looking like the rest of your newsletter rather than like the Google Doc. If you’d rather it kept the doc’s own fonts and colours, that’s the choice described in Keep the Google doc’s styling below.

That includes borders. Imported blocks are only bordered if block borders are turned on in your newsletter’s styles — if you have them switched off, imported blocks arrive with no border, the same as blocks you add by hand.

Keep the Google doc’s styling

This capability may need to be enabled for your account — contact support if you don’t see it.

If you’d rather the text looked the way it does in the doc, switch on Keep the Google doc’s styling on the Google Docs block. It sits above the Choose a Google Doc button, so set it before you bring the document in. With it on, each piece of text keeps:

• the font it was written in, as long as it’s one the composer offers — anything else falls back to your newsletter’s font, so you never end up with type the composer can’t show you
• its text colour
• any strikethrough

Everything else still comes from your newsletter’s styles, as above. Text size is the one worth knowing about: it stays with your styles either way, so headings stay heading-sized and body text stays body-sized whatever the doc used. And if your styles put decorative lines either side of your headings, imported headings arrive without them when you keep the Google doc’s styling, since the doc’s own type is what’s on show — switch them back on for any heading from its block settings if you want both.

It’s a choice you make each time you import rather than a setting that sticks, so you can bring the same document in both ways and keep whichever you prefer.

Changed your mind about one block? Setting its Primary Font in block settings repaints that whole block in the font you pick, replacing the fonts that came in from the doc. Text Color works the other way round: colours stay as they are, so an accent you meant — whether it came from the doc or you picked it by hand on a few words — isn’t wiped out by a block-level change.

Tips

• Double-check you’re selecting the correct Google account before granting permissions, and the intended document if you have similar filenames.
• Clearly named documents reduce selection errors, and keeping the doc accessible in the connected account speeds up future imports.
• If you don’t see the integration, look in the Integrations section at the bottom of the block panel.

For everything else the composer can do, see Working in Emails.