Skip to main content
Settings & Integration page with API Integration selected, Email API selected in the sub-list, and its profile table (empty) with a New button highlighted
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

1

A customer does something

They place an order, book an appointment, ask for an OTP, or submit a contact form.
2

The bot triggers an email

That action tells ChatSyncs an email needs to go out.
3

ChatSyncs sends it through your connected provider

Using whichever profile you connected — SMTP, Mailgun, SES, etc.
4

The customer (or your team) gets it right away

No delay, no separate marketing tool involved.
Customer places an order
        ↓
ChatSyncs
        ↓
SMTP / Mailgun / SES
        ↓
Order Confirmation Email

​
Set up a provider

Click New to add a profile:
Email Profile modal with Profile Name, Host, Username, Password, Port, Encryption fields and a provider list: SMTP, Mailgun, Postmark, SES, Mandrill
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:
ProfilePurpose
SMTPOrder confirmations
MailgunMarketing campaigns
Amazon SESInternal 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 IntegrationAuto Responder Integration
SendsImmediately, one email at a timeLater, through a marketing platform
Used forOTPs, confirmations, invoices, notificationsNewsletters, offers, follow-up campaigns
Who sends the emailChatSyncs, directlyMailchimp, Brevo, etc.
ProvidersSMTP, Mailgun, Postmark, SES, MandrillMailchimp, Brevo, ActiveCampaign, Mautic, MailWizz
If you want to build an email list and send marketing campaigns later, use Auto Responder Integration instead.

​
Frequently asked

Yes — connect an email provider under Email Integration, then reference that profile from a bot flow or automation step that sends email.
SMTP, Mailgun, Postmark, SES, and Mandrill.
Yes — add multiple profiles (e.g. one SMTP profile, one Mailgun profile) and choose the right one per flow or automation.
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.
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.