Connect by JBRH Open Connect

Email attachments

Connect keeps each file attached to an email, linked to its message, its business and its workspace, and lists it beside the body. A person who may see that business can download it. A program is recorded without its bytes, a file over 40 MB is recorded as too large, and a reply Connect writes by itself never carries a file: only a person attaching one in the composer does.

Status
Available What this means
Audience
both
Channels
email
In the app
#/inbox, #/data
Last verified
Product version
6.3.2

What is kept for each attachment#

A MIME message is a tree of parts. Each part the message attaches becomes one attachment record on the canonical message, written by one service for every channel that receives files: the Owner's and customers' email, and WhatsApp. The same bytes arriving twice, forwarded or sent once by email and once on WhatsApp, are stored once in the workspace and linked twice; they are never shared across workspaces.

FieldWhat it holds
filenameThe part's own filename, decoded.
mime, declared_mimeThe media type Connect will serve it as, and the one the sender declared.
size, sha256The length and fingerprint of the bytes, so a duplicate is recognised.
stateready (stored), blocked, too_large or failed, with the reason in error.
business_idThe business the message belongs to; empty when it could not be decided.

Who can open it#

Every read goes through one rule: the person's workspace, the businesses that person may see, and the business the request is operating. A file whose business could not be decided is readable by workspace admins only. A download is never content-sniffed, and a file is shown inline only when its type is one a browser may safely display here; HTML and SVG never are.

What is recorded without its bytes#

  • A program or other executable type: blocked, kept as a record without the bytes.
  • A file over the 40 MB kept per attachment: too_large.
  • A part the provider would not hand over: failed, tried again on the next delivery, up to five times.

Nothing a customer sent is silently dropped: each of these stays visible beside the message, with its reason.

When the attachment was the message#

A draft is grounded in approved Knowledge, in memory about the person and in the text of the conversation — see How a reply is drafted. A message whose meaning lived in a PDF therefore reaches the drafting step with little to read, and what comes back is written from the covering note. Those are the threads worth checking before approving.

  1. Give the thread a one-line direction saying what the document contains — Giving guidance on a thread.
  2. Or add it through Files and data in Connect, the one service both audiences and the Assistant share.
  3. Link it to the person, deal or case it belongs to, so it appears on that record rather than only on the message.
  4. Then ask a question of it, or have a new version produced from it, through Connect Assistant.

On the way out#

Connect attaches no file to a message it writes by itself. A person can attach up to ten files of up to 25 MB each in the composer, and a booking carries its calendar invitation. Cold outreach stays plain: nothing attached, no tracking pixel, no invented Re: or Fwd: prefix — see Outreach email versus a customer reply.

Questions#

Can I open a document from inside Connect?

Yes, if you may see the business the message belongs to: it is listed beside the message and downloads from there. A blocked, too large or failed file shows its reason instead.

Does an image attachment get proxied like a remote image?

No. An attached image is stored with the message and served by Connect under the rule above. Proxying is for images a message points at on someone else's server — see Remote images in email.

Will Connect attach files to the replies it writes?

No. Only a person attaching a file in the composer sends one, and a booking its invitation.