> ## Documentation Index
> Fetch the complete documentation index at: https://flywheel.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Send One-to-One Email

> Send personal, individual emails that appear to come directly from team members

<iframe src="https://app.flywheel.cx/doc-comp-previews/workflow-node-preview?type=send_one_to_one_email" title="Workflow Node Preview" width="100%" height="250px" className="border dark:border-[#1C1C20]  rounded-xl" />

## How Send One-to-One Email Works

Send personal, individual emails that appear to come directly from team members. These emails are optimized for personal communication and typically see higher engagement rates than marketing emails.

<Warning>One-to-one emails do not respect user marketing email opt-out settings. They should be used sparingly and only when necessary.</Warning>

## Configuration

<Columns cols={2}>
  <Card title="Inputs">
    <ParamField path="Send to" type="string" required>
      The ID of the user who will receive the email.
    </ParamField>

    <ParamField path="Send From" type="string" required>
      The ID of the team member the email will appear to come from.
    </ParamField>

    <ParamField path="Content" type="object" required>
      The HTML content of the email. Supports rich formatting and dynamic variables.
    </ParamField>

    <ParamField path="CC Emails" type="string[]">
      Additional CC recipients for team notifications and compliance.
    </ParamField>

    <ParamField path="BCC Emails" type="string[]">
      Additional BCC recipients for blind copy notifications.
    </ParamField>

    <ParamField path="Complete on Send Failure" type="boolean" required>
      Whether to stop the workflow if the email fails to send. Set to `true` to halt on failure, `false` to continue.
    </ParamField>
  </Card>

  <Card>
    <iframe src="https://app.flywheel.cx/doc-comp-previews/workflow-config-preview?type=send_one_to_one_email" title="Workflow Config Preview" width="100%" height="700px" className="" />
  </Card>
</Columns>

<Card title="Outputs">
  <ParamField path="status" type="enum" required>
    The status of the email send operation: `success`, `failure`, or `skipped`.
  </ParamField>

  <ParamField path="to_id" type="string" required>
    The ID of the user that the email was sent to.
  </ParamField>

  <ParamField path="email_id" type="string">
    The ID of the email that was sent (available on success).
  </ParamField>

  <ParamField path="create_email_options" type="object">
    The options used when creating the email (available on success).
  </ParamField>

  <ParamField path="create_email_response" type="object">
    The response from the email creation service (available on success).
  </ParamField>

  <ParamField path="code" type="enum">
    The code indicating why the email send operation failed or was skipped: `resend_error`, `duplicate_email`, or `user_marketing_email_opt_out`.
  </ParamField>

  <ParamField path="error_message" type="string">
    The message of the error that occurred (available on failure).
  </ParamField>

  <ParamField path="sender_config_id" type="string" required>
    The ID of the sender configuration used for the email.
  </ParamField>
</Card>

## Use Cases

**Customer Success Outreach**

```
From: sarah@yourcompany.com
Subject: "How's your experience with [Product] going?"
Content: Personal check-in from assigned CSM
To: High-value customer who hasn't been active recently
```

**Sales Follow-up**

```
From: john@yourcompany.com
Subject: "Quick question about your trial"
Content: Personalized sales follow-up based on trial usage
To: Trial user approaching end of trial period
```

**Support Follow-up**

```
From: support-team-member@yourcompany.com
Subject: "Following up on your recent support ticket"
Content: Personal follow-up to ensure issue resolution
To: Customer who recently had a support ticket resolved
```

**Onboarding Check-in**

```
From: customer-success@yourcompany.com
Subject: "How are things going with your setup?"
Content: Personal check-in during onboarding process
To: New customer in the middle of onboarding
```

## Best Practices

**Personal Touch**

* Use conversational, less formal tone compared to marketing emails
* Include personal details about the customer's situation
* Reference specific interactions or usage patterns

**Sender Selection**

* Choose appropriate team members based on the relationship
* Use the customer's assigned CSM or account manager when possible
* Ensure the sender is prepared to handle responses

**Content Strategy**

* Keep emails focused and actionable
* Include clear next steps or calls to action
* Personalize content based on user behavior and preferences

**Response Management**

* Ensure senders are prepared to handle replies
* Set up appropriate email routing for responses
* Monitor response rates and engagement metrics
