Email builder
Create JSON prompts for email marketing and lifecycle sequences
Use the server-side builder for promo emails, welcome flows, reactivation, cart abandonment, and launch communication.
Create an SEO article about choosing a CRM for a small business. Include structure, FAQ, and a clear CTA.
- Common fields + category settings + humanization
{
"category": "email",
"task": "...",
"common_settings": { ... },
"category_settings": { ... }
}Builder
Builder: Email
Start with the common settings, then tune the category-specific fields and generate a ready-to-use JSON prompt.
Quick start
Pick a ready-made scenario to populate the form with solid defaults, then fine-tune the details manually.
Welcome email
For a first-touch email that welcomes, sets expectations, and guides the next step.
Promo launch
Designed for launch emails with a clear offer, deadline, and visible CTA.
Reactivation email
For win-back emails that re-engage inactive subscribers without excessive pressure.
Describe the plain-language request in your own words. This value will be stored as the task field in the final JSON.
Common settings
These parameters affect the result regardless of the selected category.
Who the content or prompt is primarily written for.
Beginners: an audience with limited experience that needs a clear explanation.
Which language the model should use in the generated result.
English: the output should be written in English.
How concise or detailed the final output should be.
How the final output should sound emotionally.
Friendly: warm, light, and easy to understand.
How the final output should be organized and presented.
Concise: minimal fluff and maximum substance.
In what format the model should return the result.
HTML: the result should be returned in HTML.
Reduces recognizable AI markers, makes the tone feel more natural, and lets you explicitly exclude common AI phrases.
Choose the phrases and constructions the model should avoid.
List additional phrases or constructions to avoid. Use one phrase per line.
Category-specific settings
These fields depend on the selected category and its use case.
What professional role the model should take.
Email copywriter: writes emails people open, read, and click.
What type of email content should be created.
Promotional email: pushes an offer, promotion, or product.
What function the email should perform in the sequence.
Single email: a standalone one-off message.
What main result the email should deliver.
Sales: the email should lead to a purchase.
What stage of the relationship the recipient is in.
Cold audience: the person knows little or nothing about you.
How the email subject line should look in the inbox.
Curiosity: creates intrigue and makes people want to open.
How the preview text should support the subject line.
Expands the subject: explains and strengthens the subject line.
What structure should be used for the email.
Hook -> body -> CTA: moves quickly toward the action.
How personal the email should feel.
What to include to strengthen trust inside the email.
You can choose multiple options.
How strongly the email should push the reader to act now.
What the reader should do after reading the email.
Click through: drives the reader to a page or offer.
How often the call to action should appear inside the email.
Result
Generated JSON prompt
Use the generated JSON prompt right away: copy it, download it, and drop it into any AI workflow or internal tool.
The email builder standardizes work across welcome emails, nurture sequences, promotions, reactivation flows, and post-purchase communication.
It includes controls for email type, campaign goal, funnel stage, subject-line style, preview text, personalization, proof elements, and CTAs.
This makes it useful both for CRM marketers and for launch teams that want to test messaging faster and more consistently.
FAQ
FAQ
Does the builder work for both one-off emails and sequences?
Yes. You can choose single email, broadcast, sequence email, and trigger-driven scenarios.
Can I control the subject line and preview text separately?
Yes. The email category includes dedicated fields for subject-line style and preview-text style.
Is personalization configurable?
Yes. The builder includes a separate personalization-level control.
Are the raw email configs stored in the client?
No. The client only receives the form data needed for the current page and the generated result, while the full config stays on the server.