Sembot — Documentation

English

Polski

English

Polski

Appearance

Email Integration ​

Table of Contents

How to configure a sending mailbox ​

Sending emails from within a task requires a connected Gmail account. The connection can be made in two ways:

  • Directly from a task — in the Email Inbox tab, the From field displays a "Continue with Google" button. Clicking it launches the standard Google OAuth authorization flow without leaving the task.
  • From the Connections section — by adding a Google connection with Gmail access in the workspace settings.

After authorization, the Gmail account is available as a sender option in all tasks within that workspace.

Composing and sending emails from a task ​

From the task card (the Email Inbox tab in the communication section), you can compose and send an email message. The form includes the following fields:

  • From — select the connected Gmail account
  • To — recipient address
  • CC — additional recipients
  • Subject
  • Body — rich text editor with formatting and attachment support

The sent message is saved in the task's communication history and is visible in the Email Inbox tab.

Creating tasks from incoming emails ​

Sembot supports automatic task creation from incoming email messages through integration with Make.com. Make.com monitors a designated mailbox and forwards new messages to Sembot via a dedicated API endpoint.

When a new message is received (that is not a reply to a previous email), the system automatically creates a new task — the task title corresponds to the email subject, and the message body is added to the description. The email is visible in the task card under the Email Inbox tab.

Replying by email and task association ​

The system tracks email threads based on standard RFC 5322 headers (Message-ID and In-Reply-To). As a result:

  • A new message (not linked to an existing thread) → creates a new task
  • A reply to an existing message → is automatically assigned to the same task as the original message

This means that all correspondence within a single email thread is routed to one task — regardless of how many messages are exchanged. Routing is handled on the Make.com side.