Skip to content

Inbound Email

Inbound Email gives your workspace its own forwarding address. Anything sent to that address — invoices, statements, receipts, supplier replies — lands in BotBoss as a row in a table, with its attachments saved alongside, so you and your agents can search it, query it, and act on it. There is nothing to install and no mailbox to connect: you forward, BotBoss files it.

What you can do

  • Turn email into data. Every message becomes a row you can filter, sort, and query like any other table in your Database — sender, subject, body, attachments, and when it arrived.
  • Keep attachments with the message. PDFs, spreadsheets, Word documents, images, and CSV or text files are saved as files and linked from the row.
  • Choose who can send to you. An optional source filter accepts or rejects messages by sender address.
  • Decide how much happens automatically. By default you triage each email yourself. You can instead have an agent propose an action for your approval, or run a workflow you designed. Nothing is ever acted on without a person approving it.
  • Clean up on a schedule. Optionally delete email rows older than 7, 30, 90, or 365 days. The default keeps everything.

How it works

  1. Create the connection. Open the Connectors page (under Connections), find Inbound Email, and click Connect. Give the connection a name — for example, "Accounts payable".
  2. Generate a signing secret. The form asks for one before it lets you create the connection: click Generate signing secret. You only need to copy it if you deliver mail to BotBoss from your own mail provider's webhook; if you simply forward mail to the address, you can leave it as is. It is stored encrypted and masked.
  3. Pick where mail lands. Under Target table, choose an existing table, or leave it on Auto-create on first email and BotBoss creates a dedicated table when the first message arrives.
  4. Set the optional controls. Source filter (who may send), Retention (how long to keep emails), and Processing (Manual, Agent, or Workflow). Then create the connection.
  5. Forward to your address. Open the connection again and copy the Forwarding address — it looks like ap-acme-8sQ2v…@inbox.botboss.com. Send or auto-forward mail to it: from your mail client, a forwarding rule in Gmail or Outlook, or a supplier's "send invoices to" field.

Within a few seconds of a message arriving, a new row appears in the target table.

What lands in the table

Each email becomes one row with the sender, subject, plain-text body, an HTML version of the body when the message had one, the attachments, the message ID, the time it was received, and a Sender Verified value.

Sender Verified is true only when the receiving mail system confirmed the message really came from the address it claims; it is false when that check failed and unknown when there was no answer. Treat the From address as unconfirmed unless Sender Verified is true — anyone can put any address in a From line. For that reason, Agent and Workflow processing only run on emails from a verified sender; every other email still lands in the table and waits for you.

HTML bodies are cleaned before they are stored: scripts and other active content are removed, and images hosted elsewhere are not loaded by default.

Attachment limits

  • Accepted types: PDF, Word and Excel files (both current and legacy formats), PNG, JPEG, and GIF images, and CSV or plain text. BotBoss checks the actual file contents, not the name or the type the sender declared, and refuses a file that is not what it claims to be.
  • Up to 25 MiB per attachment, 20 attachments per email, and 30 MiB for the message body.

Example: send supplier invoices to a table

  1. On the Connectors page, connect Inbound Email, name it "Supplier invoices", generate the signing secret, and leave Target table on Auto-create on first email. Leave Processing on Manual.
  2. Reopen the connection and copy the Forwarding address.
  3. In your mail client, forward one existing supplier invoice to that address.
  4. Open the new table in Database. The invoice email is a row, and the PDF is a linked file.
  5. When you trust the setup, set a Source filter so only your suppliers' domains are accepted — add .*@acme\.com under Sender allowlist (one pattern per line) — and ask an agent to summarize the new rows each morning.

Good to know

  • The address is the credential. Anyone who knows it can send to it, so share it only with the senders you expect and use the source filter to narrow it. If an address leaks, delete the connection and create a new one.
  • Every connection has its own address, table, and settings. You can create more than one — for example, one for invoices and one for statements.
  • Access is permissioned like any other connector. Agents see the emails only when you grant them the connection.
  • BotBoss does not run a mailbox. Mail arrives through a managed inbound service, and messages that are filtered out or over the limits are not added to your table.

Troubleshooting

What you see What it means What to do
Nothing appears after forwarding The message did not reach the address, or the source filter dropped it. Check the address was copied exactly, and that the sender matches your Sender allowlist (and is not on the blocklist).
The email arrives without an attachment The file type is not accepted, is over 25 MiB, or its contents did not match its type. Send it as a PDF, spreadsheet, image, or CSV, under the size limit.
Sender Verified is false or unknown The receiving mail system could not confirm the sender. Do not rely on the From address. Agent and Workflow processing skip these emails, so review them yourself.
"Generate a signing secret first" when creating The signing secret is required before the connection can be created. Click Generate signing secret, then create the connection.