Prompt Guide

Brew generates emails from natural-language prompts. The more specific you are about goal, audience, and tone, the better the first draft.

​

Prompt Patterns That Work

• Lead with the goal. “Announce our new analytics dashboard” is better than “Write a marketing email.”
• Name the audience. “For new SaaS trial users who haven’t booked a demo yet” gives Brew the context to pick the right tone.
• Specify length and structure. “3-email welcome flow” or “single email with one CTA and a testimonial” keeps Brew focused.
• Reference brand assets. Mention domains (“use the brand from acme.com”), Figma URLs, or attached images directly in the prompt.
• Iterate after generating. Don’t try to get everything in one prompt. Generate, review, and tell Brew what to change.
• Ask for personalization by name. “Open with a greeting that uses the contact’s first name and falls back to there” puts a real merge tag in the copy instead of a placeholder Brew invented.

​

Generate Multiple Emails at Once

A single prompt can produce several emails. They appear side-by-side on the canvas.

• “Create three subject-line variations for this announcement.”
• “Generate two versions of this welcome email, one playful, one professional.”
• “Build a 5-email welcome series and lay them out on the canvas.”

This is one of Brew’s most useful patterns: explore options without losing the original.

​

Automation Prompt Patterns

Describe the trigger, timing, and outcome when you ask Brew to build an automation. These prompts cover common starting points: Welcome flow. Multi-step. Triggered when a new user signs up.

“Build a 3-step welcome flow triggered by user_signup. First email welcomes them and sets expectations. Second email sends a quick-start guide. Third email shares a customer success story.”

Abandoned cart. Multi-step. Triggered by a cart_abandoned event that your store fires when someone leaves a cart without checking out.

“Build an abandoned-cart flow for cart_abandoned. First email: friendly reminder with the items. Second email 24 hours later: address common objections. Third email 48 hours later: limited-time discount.”

Order confirmation. Single-email automation. Triggered when an order is placed.

“Create an order confirmation email triggered by order_placed. Include the recipient’s first name, order number, items, total, and shipping ETA.”

A single-email automation like this respects unsubscribes when it sends from a marketing-purpose domain. For a message that must reach unsubscribed contacts, a password reset especially, point its send step at a domain with a transactional sending purpose. That’s Brew’s transactional email, with no unsubscribe footer. Re-engagement. Multi-step. Run once for an audience of inactive contacts, and run it again each cycle with a fresh audience. Brew has no scheduled trigger.

“Build a 3-step re-engagement flow. First email: ‘We miss you’ with new features. Second email three days later: ask what content they’d prefer. Third email: final chance to stay subscribed.”

For the complete build, test, and publish workflow, see Build an Automation.

​

@-Mention Existing Work

In chat, type @ to reference an existing email or automation. Brew uses the mentioned item as context for the new request.

• “Match the tone of @welcome-email-v2 for this onboarding flow.”
• “Build an automation that fires after @abandoned-cart but for high-value customers.”

A typeahead suggests recent emails and automations as you type.

​

Attach Files and Links

Attach files directly to a prompt to give Brew exact assets to work with.

• Images. Drag in product photos, hero shots, or screenshots. Brew uses them in the email or as style references.
• Figma URLs. Paste a Figma frame URL with node-id. Brew converts the design to a responsive email.
• HTML. Paste full HTML to remix an existing email into your brand.

​

What Brew Can Do While Generating

Brew reaches for these on its own, based on what the prompt asks for. You can also ask for any of them by name. Brand and layout

• Use another brand. Name a domain and Brew pulls its colors, fonts, and logo. “Use the brand from acme.com for this co-marketing email.”
• Use a known layout. Product grids, pricing tables, and hero sections are patterns Brew already has. “Use a 3-column product grid.”
• Match a style. Describe the feel instead of the layout and Brew finds examples to shape structure and tone. “Make it feel like a luxury fashion promotion.”
• Footer icons. Social and app-store icons come correctly sized. “Add social icons in black to the footer.”

Images

• Generate an image. Describe it and Brew creates a hosted image. Camera, lighting, and material details work better than abstract descriptions. “A laptop on a wooden desk in warm morning light.”
• Match a reference. Point at an image you already use and new imagery follows its style. “A product shot in the style of our OG image: product on linen, soft light.”
• Edit or retouch. Color, warmth, contrast, small composition changes. “Make the hero warmer and more contrasty.”
• Remove a background. Returns a transparent PNG. “Remove the background so I can place the product on a gradient.”
• Animate a still into a GIF. Keep it to one or two per email, on the hero or a product, and keep each light enough to load fast on a phone. “Animate the hero image.”
• Analyze a screenshot. Attach a screenshot of a site or an email and Brew reads it for structure and copy. It never embeds the screenshot itself. “Look at this and tell me what to improve.”

Research

• Look something up. Brew searches the web for live facts before writing copy. “Check the current pricing on our competitor’s site before drafting the comparison.”

The image steps are also on the Public API, each charged in credits. The API Catalog lists the endpoints and costs.

​

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you: