> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/integrations/integrations-imap-and-smtp.md).

# Integrations - IMAP and SMTP

SprintHub allows integrating email accounts via **IMAP**, enabling sending and receiving messages directly within the platform.

⚠️ **Important:** this article is intended for IMAP accounts from any provider, including **custom domains and Google accounts (Gmail/Workspace)**.\
Outlook accounts **Outlook** have a specific process — see the dedicated tutorial.

{% content-ref url="/pages/5b717c4a3c4a50b8ca93aa5e49f696d11bbbc2c4" %}
[Integrations - Outlook](/en/topics/integrations/integrations-outlook.md)
{% endcontent-ref %}

{% content-ref url="/pages/613076f7d6d57092bc5c5a44ce33a48f4719c2e3" %}
[Integration - Google Ads and Gmail](/en/topics/integrations/integration-google-ads-and-gmail.md)
{% endcontent-ref %}

***

#### 🔧 Step-by-step setup

1. **Access the email settings**
   * Click the **gear** icon in the top-right corner of SprintHub.
   * Go to **“System Settings”** > **“Integrations” >> “IMAP”**.
2. **Add a new account**
   * Click **“Add email account”**.
   * Choose the **“IMAP/SMTP”**.
3. **Fill in your account information**\
   Enter the details provided by your email provider:
   * **Email address:** your full address (example: [contact@yourdomain.com](mailto:contato@seudominio.com))
   * **User:** usually the same as the email
   * **Password:** account password or app password
   * **IMAP server:** `imap.yourdomain.com`
   * **IMAP port:** 993 (with SSL)
   * **SMTP server:** `smtp.yourdomain.com`
   * **SMTP port:** 465 (with SSL)
4. **Test the connection**
   * Click **“Test connection”** to confirm that everything is working.
   * If the test is successful, click **“Save”**.

***

#### 💡 How to configure Gmail IMAP (Google Workspace)

If you use **Gmail or a Google Workspace account**, follow this specific step-by-step guide:

1. **Enable IMAP in Gmail**
   * Go to [https://mail.google.com](https://mail.google.com/).
   * Click the **gear** ⚙️ > **“See all settings”**.
   * Go to the tab **“Forwarding and POP/IMAP”**.
   * In **“IMAP access”**, select **“Enable IMAP”**.
   * Click **“Save changes”**.

<figure><img src="/files/51c43d8a32b55eabd3f416680a32a88ded3a4e44" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/8a45cd71d1e329ce38df79af6c7d5c140a029a0a" alt=""><figcaption></figcaption></figure>

2. **Generate an app password**

* Go to <https://myaccount.google.com/security>.
* Enable **two-step verification** (if it's not enabled yet).

{% hint style="danger" %}

### Important

**App passwords are only available when two-step verification is already enabled on the account.**\
If this option does not appear, first check whether two-factor authentication has been configured correctly. After enabling it, the option to generate app passwords will appear.
{% endhint %}

* Then, click **“App passwords”**.
* Choose **“Email”** as the app and **“Other (custom)”** (for example: “SprintHub”).
* Click **Generate** and copy the 16-digit password displayed.

3. **Use this password in SprintHub**

* In the **Password**field, enter the **app password** (not the normal Google account password).
* Fill in the other fields like this:
  * **IMAP server:** `imap.gmail.com`
  * **IMAP port:** 993 (SSL)
  * **SMTP server:** `smtp.gmail.com`
  * **SMTP port:** 465 (SSL)

4. **Test and save**

* Click **“Test connection”**.
* If the test is successful, click **“Save”**.

{% embed url="<https://www.youtube.com/watch?v=7lG9XMvCGH4>" %}

***

#### ⚙️ Important tips

* Check whether the **user and password** are correct.
* Confirm that **IMAP access** is enabled in your email provider.
* Some providers (such as Google, Zoho, Umbler, Locaweb, etc.) require **app passwords** instead of the normal password.
* If the test fails, check the **ports and servers** used.

***

#### 📩 Understanding IMAP and SMTP

* **IMAP** is the protocol responsible for **receiving and synchronizing emails** between the server and SprintHub.
* **SMTP** is the protocol used to **send emails**, including **mass sending** and automated communications.

> 💡 In other words: the IMAP setup is only for **receiving messages**, while the **mass sending** must be done using a **SMTP account** configured specifically for this.

To set up your SMTP account for mass sending, see the dedicated tutorial:

{% content-ref url="/pages/c209e8840de60a890a5587d19fb9645eae66162c" %}
[Email](/en/topics/system-settings/email.md)
{% endcontent-ref %}

***

### Configuring the Integration with SAC 360°

<figure><img src="/files/05cb572394185439a8d4ac27b210fbba2238fe7f" alt=""><figcaption></figcaption></figure>

When accessing the email account settings, you will find the following options:

By enabling this option, the email account starts working as a customer support channel in SAC 360°.

* Each email received from a **new contact** automatically creates a support ticket in SAC 360°.
* Message reception occurs via the protocol **IMAP**, with automatic synchronization every **1 to 5 minutes**.

> **Important:** Only new contacts automatically create a support ticket. Other messages are linked to the existing history.

***

### Mark emails as read

Defines the behavior of emails in the provider's inbox after they are synchronized.

#### Enabled

After being imported into SprintHub, emails are automatically marked as **read** in the provider's inbox.

#### Disabled (Default)

Emails remain **unread** in the provider's inbox, even after being synchronized with SprintHub.

***

### Conversation Model

Defines how messages will be organized within the support ticket in SAC 360°.

#### Continuous Conversation

Displays the contact's entire email history in a single support ticket, making the full communication easier to view.

Recommended for teams that want to follow the customer's entire journey in a single conversation.

#### Ticket

Each support ticket has its own message history, showing only the emails related to that specific ticket.

Recommended for teams that work with independent tickets and want to keep each request separate.

***

### Sender Name

Defines which name will be displayed in the **"From"** field of emails sent by SAC 360°.

#### Account Name

Uses the name configured in the email account itself.

**Example:**

**SprintHub Support** [support@company.com.br](mailto:suporte@empresa.com.br)

#### Agent Name

Uses the name of the user responsible for the support.

**Example:**

**João Silva** [support@company.com.br](mailto:suporte@empresa.com.br)

***

#### ✅ Done!

Your IMAP account has been successfully configured in SprintHub \
Now you can **receive and view your emails** directly on the platform, keeping all communication centralized and organized.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/integrations/integrations-imap-and-smtp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
