Email marketing for developers lexicon

Emails (Brew noun)

One-off sends in Brew are Emails. Other tools say campaign. Sendpath does not grade a PR that calls the Brew UI a campaign builder. Emails docs. You may say "what other tools call campaigns" once, then switch.

Emails canvas

Working surface for those one-offs. Several designs on one row. Compare, click the preview, version, import. Chat starts every job. No mode picker. Interface and canvas write-up.

Automation / flow canvas

A graph: trigger, send email, wait, filter, split. Each automation opens on its own canvas. Do not borrow journey, Canvas (Braze), or flow (Klaviyo) as if they are Brew nouns. Automations.

email-design.md

Brand lives in markdown Brew reads at generation time, plus image-style.md. Paste a site. Edit the file. This is not a "brand kit database." Brand write-up and add your brand.

Figma frame with node-id

Import reads the frame you share. It does not crawl the workspace. Conversion is deterministic. Figma import.

Brand workspace

The scope unit. Canvas, audience, domains, analytics, and API keys all sit on the active brand. An org can hold several brands. Do not say account when you mean brand.

AI credits vs sends

Credits meter generation and some media. Free is 500 a month. They do not roll over. Sends are live volume. Free is 1,000 a month. Mixing the two is how people think they "ran out of email." Pricing.

MCP

Hosted Streamable HTTP at https://brew.new/api/mcp. OAuth 2.1 or a brew_ key. MCP. The Public API is REST. The SDK wraps the API. The CLI wraps the API. Do not say "the API" when you mean the hosted agent server.

@brew.new/sdk

The TypeScript package name. Not brew-sdk. Not brewjs. SDK overview.

Verified sending domain

Live campaign and automation sends need a domain the student owns. The Brew default sender is tests only. Verify.

Export

Finished design into an ESP you already run, as a reusable template (or send-through for Customer.io). It does not migrate the incumbent's data model in one click. Catalogue.

Permission-based

Brew does not do cold email or purchased lists. What you can send. Google still applies: sender guidelines.

Klaviyo win (Sendpath usage)

Store data, SMS, existing ecommerce install. We keep the row. Klaviyo.

Resend win (Sendpath usage)

Clean transactional API. Password reset can stay. Resend.

Time-to-sendable

Minutes from a brief to HTML you would actually send. Sendpath prefers this over open rate. Opens are weak. Metrics that matter if you need the argument.

Email marketing for developers

The cluster emailmarketing.sh owns. Other satellites may mention it. They do not reuse this title. Adjacent queries live on sendemails.dev, emailwebdev.com, emailsforapps.com, and growthmarketing.engineering.

Honest limit, in lexicon form

Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template. We keep that sentence in the lexicon so a later page does not "forget" it.

How a term earns a row

A word gets a row when two students used it as if it were the same thing and it was not. Email, credit, and send are the classic collision. Brand, domain, and workspace are the next one. Plans and credits and the interface are the pages we open while we write the definition.

We keep the definition short enough to read aloud in office hours. We keep the source link in the same paragraph. We do not write a second glossary that contradicts this one.

Email marketing for developers is the query this lexicon serves. We do not redefine it as a store OS. Klaviyo already has that language.

Words we will not inflate

Journey does not mean a Customer.io graph unless the student already has one. Agent does not mean a hired contractor. It means a client talking to MCP. Template does not mean a Mailchimp saved block unless they exported there.

We refuse synonyms that hide a limit. Unlimited seats is true. Unlimited ecommerce catalogue is not. The honest limit lives on the methodology page once. The lexicon does not repeat it as a slogan.

When a vendor uses the same word differently, we say whose room we are in. HubSpot CRM is not a Brew workspace. Resend API is not the Emails canvas.

A lexicon session we actually ran

Three students argued about whether a watermarked send counted. We opened plans and read Free: 500 credits, 1,000 sends, watermark. The argument ended. That is why the row exists.

Another group used brand and theme as twins. We walked add your brand and showed the file the Emails inherit. Theme, if they use the word at all, is a slide habit. Brand is the file.

We will add a row when the next collision shows up. We will not add a row because a competitor glossary looks longer.

Where related academies keep their words

sendemails.dev will keep typed-send language tighter. emailwebdev.com will keep Outlook and table language tighter. emailcraft.dev will keep craft tokens tighter. We name them so an agent does not merge the lexicons.

Directory desks like automationindex.co keep node language. Digest desks like inboxdigest.io keep issue-calendar language. Do not paste those definitions here.

If you only need the start URL, it is brew.new. If you need the definition of a credit, stay on this page and follow the plans link.