How One-to-One Email works
One-to-One Email sends a personal email from a configured team member sender using content defaults you define in the builder. Unlike marketing emails, these messages appear as direct communication from a real person on your team, making them ideal for relationship-driven outreach. The builder controls the sender identity, subject, and body content, while the agent handles timing and recipient selection during the run. This ensures every one-to-one message maintains a consistent, personal tone while still being triggered automatically based on user behavior or lifecycle stage.An agent’s one-to-one email skips anyone who opted out of marketing email: the send returns
skipped with the code user_marketing_email_opt_out, and nothing goes out. A one-to-one email step in a workflow does not check the opt-out.Configuration
Inputs
Outputs
The options used when creating the email, including subject, body, CC, and BCC settings (available on success).
The code indicating why the email send operation failed or was skipped. Can be
resend_error, duplicate_email, or user_marketing_email_opt_out.Use cases
Lifecycle HandoffBest practices
Sender Identity- Map the sender to the team member who actually owns the relationship with the recipient.
- Avoid using generic or shared sender identities — one-to-one emails should feel personal.
- Use
from_idoutput to verify the correct sender was used in each delivery.
- Follow successful sends with Set Custom Property to mark that outreach has been completed.
- Enable
complete_on_send_failurewhen the agent run should proceed regardless of email delivery status. - Monitor
codeoutput values likeduplicate_emailto prevent repeat outreach to the same user.
- Keep email content defaults up to date and aligned with your team’s current voice and messaging.
- Review templates regularly to ensure they reflect current product state and company positioning.
- Use preview text to reinforce the subject line and improve open rates in recipient inboxes.