# Email Service

## Overview

The Email Service connector enables DBSync workflows to retrieve and process incoming emails, allowing email data to be used as input for automation and integration processes. The Email Service connector receives and reads email messages automatically through standard email protocols such as IMAP servers. So, the organizations can integrate email communications directly into their workflows. This allows them to retrieve the latest emails or filter them based on defined criteria, or capture inbound emails for processing within DBSync integrations.

This connector is used to read incoming emails and integrate email data with other systems. It enables organizations to process inbound messages and extract valuable information for downstream workflows. The Email Service connector supports inbound request processing, email-driven workflows, and automated data extraction from incoming messages.

## Key Benefits

#### For Business Users

* Inbound Email Processing: Capture incoming emails and process them within automated workflows.
* Reduced Manual Effort: Eliminate manual email handling by automating inbound email capture

#### For Technical Teams

* Workflow Integration: Easily incorporate received emails into DBSync projects, tasks, and automation rules.&#x20;
* Reusable Connector Instance: A single configured email connector can be reused across multiple processes, workflows, and projects within a project.

## Prerequisites

Before configuring the Email Service Connector, ensure that:

* DBSync Access: You have a valid DBSync Email Service Connector license along with credentials to access the DBSync iPaaS platform.
* Email Server Credentials: Valid email server credentials including username, password (AppPasswords), host, and port details.
* Inbound Email Access: IMAP access enabled, if receiving emails through the connector.

> **Note:** Ensure that you create an AppPassword for services like Gmail instead of using a standard login password before using the email connector to read your email. Refer to your email provider documentation for steps to generate an AppPassword.

## Quick Setup Guide

Follow these steps to configure Email Service connector:

1. **Login to DBSync Cloud Workflow**
   * Use your DBSync credentials to access the platform.
2. **Add the Email Service Connector**
   * Navigate to the Connectors list  in the Apps pane and select Email Service connector.
3. **Enter Your Email Service Details**
   * **Username**: Username of the email account on the email server (IMAP)
   * **Password**: Password for the email account (AppPassword)
   * **Protocol**: Email protocol used by the connector
   * **Host**: Email server host name or IP address
   * **Port**: Server port number&#x20;
   * **SSL**: Indicates whether SSL encryption is enabled (true or false)

**Note**: If SSL is required, consult your system administrator to confirm the appropriate configuration settings.

<div align="left"><figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FlAyb0vobGD9TcyDCfwE6%2Funknown.png?alt=media&#x26;token=0327fd83-b5b6-4db8-8585-1b5ff4ed6b7d" alt="" width="563"><figcaption></figcaption></figure></div>

4. **Test Connection**
   * Use the Test Connection button to verify access permissions and connectivity.
5. **Save Configuration**
   * Once validated, save the connector for use in workflows and projects.
6. Configure **Email** Action
   1. After saving the connector configuration, ensure that you configure the Email action.

> **Note**: You can use the Email Service Connector, after you have configured the Email Action.

## Uses

The Email Service connector supports processing of inbound emails. The connector can retrieve incoming emails and trigger workflows or integration processes based on received messages.

Typical examples include:

* Processing inbound service requests
* Capturing responses from external systems
* Triggering automation workflows from email messages
* Filtering retrieved emails based on required search criteria, such as Subject, recievedFrom, date filter.

***

## Frequently Asked Questions

**Does the Email Service Connector support sending and receiving emails?**

The connector only supports retrieving inbound emails using supported email server protocols.

**Is the connector available in both cloud and on-premise environments?**

Yes. The connector is supported in both cloud (on-demand) and on-premise versions of DBSync Cloud Workflow.

**Can the connector be used across multiple workflows?**

Yes. A single Email Service connector configuration can be reused across multiple workflows and projects.

**Does the Email Service Connector support bi-directional integration?**

No. The Email Service connector is designed only for receiving inbound email messages.

**How frequently can email workflows run?**

DBSync workflows can be scheduled to run every minute.

**Can I test the connector before purchasing?**

Yes. DBSync provides a free trial that allows you to evaluate the Email Service Connector and other platform capabilities.&#x20;

## Summary

The Email Service Connector enables DBSync Cloud Workflow to retrieve and process incoming emails using standard email protocols. By capturing inbound messages and integrating them into workflows, organizations can automate email-driven processes, reduce manual effort, and streamline data flow across systems.

## Related Links

Email Action: Refer to Email action document to understand how to use it with Email Service Connector

Create AppPassword: Learn how to generate App Passwords for secure authentication with your email account.

<br>


---

# Agent Instructions: 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:

```
GET https://docs.mydbsync.com/cloud-workflow/2026_connectors_new/email-service.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
