Configuration
| Setting | Description |
|---|---|
| Email template | Select the email to send. Templates are created and managed in the email editor outside of the workflow. |
| Send to | The contact’s email address (automatically resolved from the contact record). |
Personalization
Email subject lines and body content support dynamic variables through Liquid templating. Variables are resolved at send time using the contact’s current data, so any enrichment or variable updates that happen upstream in the workflow are reflected in the email. Common variables used in emails:| Variable | Example output |
|---|---|
{{First Name}} | ”Sarah” |
{{Company Name}} | ”Acme Corp” |
{{Job Title}} | ”VP of Marketing” |
Behavior
- The node sends one email per contact that passes through it.
- The email is sent immediately when the contact reaches the node (subject to any upstream delays).
- Only contacts with a Subscribed subscription status receive the email. Contacts with Unsubscribed, Bounced, or No subscription status are skipped.
- If the email template has been deleted or is in draft state, the node is skipped and the contact advances to the next step.
Best practices
- Place enrichment before email nodes. Use Magic Enrichment or Apollo Enrichment upstream to ensure personalization variables are populated before the email is sent.
- Use delays between emails. Insert a Time Delay or Wait For node between consecutive Send Email nodes to space out delivery and protect your sender reputation.
- Branch before sending. Use a True/False Branch to check subscription status or engagement history before sending, especially for re-engagement workflows where you want to avoid contacts who have already converted.
- Test with a small audience. Activate the workflow with a test audience first to verify subject line personalization, body content, and variable resolution before scaling to your full contact base.