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

# Email Integration

> Connect an email provider (SMTP, Mailgun, Postmark, SES, Mandrill) under Control Panel → Settings & Integration so ChatSyncs can send an email the instant something happens — an order, a booking, an OTP. Use this when a customer wants a confirmation, OTP, or notification email sent immediately, not a marketing campaign (that's Auto Responder Integration).

<Frame caption="Control Panel → Settings & Integration → API Integration → Email API, with the New button highlighted.">
  <img src="https://mintcdn.com/chatsyncs/vqDfXbzggyAX9oqx/images/learn/control-panel-email-integration/step-01-email-integration-list.png?fit=max&auto=format&n=vqDfXbzggyAX9oqx&q=85&s=ac07091a0059f637b2785420ec0bbe6f" alt="Settings & Integration page with API Integration selected, Email API selected in the sub-list, and its profile table (empty) with a New button highlighted" width="1264" height="531" data-path="images/learn/control-panel-email-integration/step-01-email-integration-list.png" />
</Frame>

**Email Integration** connects ChatSyncs to an email provider so it can send an email
**immediately**, the moment something happens in a conversation — an order placed, an
appointment booked, an OTP requested. Nothing is stored for later; the email goes out right
away.

## How it works

<Steps>
  <Step title="A customer does something">
    They place an order, book an appointment, ask for an OTP, or submit a contact form.
  </Step>

  <Step title="The bot triggers an email">
    That action tells ChatSyncs an email needs to go out.
  </Step>

  <Step title="ChatSyncs sends it through your connected provider">
    Using whichever profile you connected — SMTP, Mailgun, SES, etc.
  </Step>

  <Step title="The customer (or your team) gets it right away">
    No delay, no separate marketing tool involved.
  </Step>
</Steps>

```
Customer places an order
        ↓
ChatSyncs
        ↓
SMTP / Mailgun / SES
        ↓
Order Confirmation Email
```

## Set up a provider

Click **New** to add a profile:

<Frame>
  <img src="https://mintcdn.com/chatsyncs/Ma-dImppMzscCHUd/images/learn/control-panel-email-integration/step-02-email-profile-modal.png?fit=max&auto=format&n=Ma-dImppMzscCHUd&q=85&s=3342800c1c8259d9d1bf5078561dedcc" alt="Email Profile modal with Profile Name, Host, Username, Password, Port, Encryption fields and a provider list: SMTP, Mailgun, Postmark, SES, Mandrill" width="526" height="538" data-path="images/learn/control-panel-email-integration/step-02-email-profile-modal.png" />
</Frame>

Supported providers: **SMTP** (any generic SMTP server — Host, Username, Password, Port,
Encryption), **Mailgun**, **Postmark**, **SES** (Amazon), and **Mandrill**.

You can add more than one profile and use a different one per purpose:

| Profile    | Purpose                |
| ---------- | ---------------------- |
| SMTP       | Order confirmations    |
| Mailgun    | Marketing campaigns    |
| Amazon SES | Internal notifications |

## Real examples

**Order confirmation** — a customer orders a laptop through the bot, and ChatSyncs immediately
sends:

```
Subject: Order Confirmation

Hello Rahul,

Thank you for your order. Your order has been successfully placed.

Order ID: #12345
```

**Appointment booking** — the bot confirms a booking, and ChatSyncs sends:

```
Subject: Appointment Confirmed

Your appointment is booked.

Date: Monday
Time: 4:00 PM
```

**OTP verification** — the customer asks for a one-time code, and ChatSyncs sends:

```
Subject: Your OTP

Your verification code is:

845921
```

**Notify your team** — instead of emailing the customer, send the email to your own team when a
lead comes in, e.g. after a contact form is filled out:

```
New Lead Received

Name: Rahul
Phone: +91XXXXXXXXXX

Message:
I need more information.
```

## Email Integration vs Auto Responder Integration

It's easy to mix these two up because both send email — the difference is *when* and *why*:

|                     | Email Integration                            | [Auto Responder Integration](/learn/control-panel-auto-responder-integration) |
| ------------------- | -------------------------------------------- | ----------------------------------------------------------------------------- |
| Sends               | Immediately, one email at a time             | Later, through a marketing platform                                           |
| Used for            | OTPs, confirmations, invoices, notifications | Newsletters, offers, follow-up campaigns                                      |
| Who sends the email | ChatSyncs, directly                          | Mailchimp, Brevo, etc.                                                        |
| Providers           | SMTP, Mailgun, Postmark, SES, Mandrill       | Mailchimp, Brevo, ActiveCampaign, Mautic, MailWizz                            |

If you want to **build an email list and send marketing campaigns later**, use
[Auto Responder Integration](/learn/control-panel-auto-responder-integration) instead.

## Frequently asked

<AccordionGroup>
  <Accordion title="Can my bot send emails, not just WhatsApp messages?">
    Yes — connect an email provider under **Email Integration**, then reference that profile
    from a bot flow or automation step that sends email.
  </Accordion>

  <Accordion title="Which email providers can I connect?">
    **SMTP**, **Mailgun**, **Postmark**, **SES**, and **Mandrill**.
  </Accordion>

  <Accordion title="Can I use two different email providers for different purposes?">
    Yes — add multiple profiles (e.g. one SMTP profile, one Mailgun profile) and choose the
    right one per flow or automation.
  </Accordion>

  <Accordion title="What's the difference between Email Integration and Auto Responder Integration?">
    Email Integration sends a single email right away (an OTP, a confirmation). Auto Responder
    Integration instead sends the customer's email address to a marketing platform like
    Mailchimp, which handles newsletters and campaigns on its own schedule — see the comparison
    table above.
  </Accordion>
</AccordionGroup>

<Warning>
  If you're using an **SMTP** provider, double-check the **Host**, **Port**, **Username**,
  **Password**, and **Encryption** settings — a mismatched port or encryption setting is the most
  common reason a profile saves successfully but emails silently fail to send.
</Warning>
