Inbox

Inbox (beta in the sidebar) gives each book an email address. You forward invoices and receipts. BeanHub stores the message and attachments so you can find them later. Optional AI extraction uses the open-source beanhub-inbox engine. You can run the same extraction locally.

Inbox appears on Git books and Connect-only books.

The address

On Inbox → Emails the text box shows:

<username>+<repository>@inbox.beanhub.io

Example: user janedoe, book mybook → janedoe+mybook@inbox.beanhub.io.

You can add extra + tags:

janedoe+mybook+SaaS+GitHub@inbox.beanhub.io

BeanHub attaches tags SaaS and GitHub to that message. Use tags to filter later.

Production domain is inbox.beanhub.io. (Local development uses a different domain. Do not send mail there.)

Receive mail

1. Copy the address.
2. Forward or BCC a receipt from your normal mailbox.
3. Refresh Emails. Click a row to read the body and download attachments.

Note

Receiving mail needs BeanHub’s inbound mail pipeline (cloud). A local copy of the app without that pipeline will show an empty inbox. This docs pass did not send live email.

Pause receiving in repository Settings by checking Pause Inbox Receiving. The address stays the same.

AI extraction

The hosted product can extract fields from invoices (paid plans advertise AI extraction). You can also dump emails and run extraction yourself:

pip install "beanhub-cli>=3.0.0"
bh login
bh inbox dump
bh inbox extract

bh inbox dump needs a signed-in CLI. bh inbox extract can run on .eml files you already have. Blog with a demo video: BeanHub Inbox. CLI: beanhub-cli inbox.

Inbox is beta. Schemas and UI can change. Keep a copy of important PDFs outside BeanHub if you rely on them for tax or audit.

Settings

Repository Settings includes timezone (used when displaying times) and the pause-inbox checkbox. Deleting an email in the UI queues cleanup of stored blobs.