Incoming Messages

The Incoming Messages section (/incoming-messages) is Orbita's unified "mailbox": emails from a connected mailbox and messages from a Telegram bot land here before turning into a record of some entity (a ticket, a request, etc.).

Where messages come from

Channel	Source
Email	Emails from an inbox connected via IMAP (configured on the IMAP tab in Settings)
Telegram	Messages to a bot connected on the Telegram tab in Settings — via webhook or long polling

Mail is checked automatically on a schedule; messages that have already been imported aren't imported again. The "Fetch mail now" button on the IMAP settings tab triggers a check manually, without waiting for the schedule.

List of incoming messages

The table shows all received messages regardless of channel:

Column	Description
ID	Internal message number
From	The sender's name and address (email) or chat identifier (Telegram); a colored channel badge sits next to it
Subject	The email subject (for Telegram, an automatically generated string) and a short text snippet
Received	Date and time of arrival
Status	New or Processed
Actions	Buttons for the actions available for that specific message (see below)

Above the table: a search box and a Refresh button.

Message statuses

• New — the message has been received but hasn't yet been turned into a record.
• Processed — an action has already been performed on the message (manually or automatically); action buttons are no longer shown for it.

Viewing a message

1. Click a message row in the table
2. A preview panel opens on the right: sender, channel, received date, subject, and message body (HTML emails are shown in a sandboxed frame, plain text as-is)
3. Close the panel with the close button in its header

The preview panel offers the same action buttons as the table, as long as the message hasn't been processed yet.

Turning a message into a record

If at least one action (rule) is configured for the message's channel, buttons with labels set by the administrator appear next to the message (for example, "Create ticket"). The list and behavior of these rules is configured on a separate screen — Incoming Actions.

Clicking an action button:

1. Requests prepared data from the server — the fields that could be collected from the message using the mapping rules
2. Marks the message as Processed
3. Opens the record creation form for the target entity, with fields already filled in — the administrator or operator just needs to review and save the record

If no action is configured for the message's channel, no buttons are shown — the message can only be viewed.

Reprocessing

Each click of an action button opens a new record creation form. There's no separate "undo processing" feature, and no automatic linking of a reply to an existing record in the interface — repeated emails on the same topic create a new record, unless the rule is written to find and update an existing one instead (see Incoming Actions).

Attachments

Email attachments (files from the message) are stored on the server and accessible via a link from the original message; when creating a record, they can be attached to it manually, or this can be done by the action's script.