Attach files and work with results

Supply files to the Assistant and inspect tables, snippets, and downloads.

Use the paperclip or drop files onto the composer. Wait for each attachment to finish uploading, then send your message. An attachment is included with the next message and gives the Assistant a reference to that file.

Give a useful request

Explain what you want done with the attachment: inspect its contents, import it into a particular app, or extract a document. Name the destination app when there is one. Attaching a file does not by itself create an app document, run extraction, or approve a proposed import.

Files are handled through their stored references. The Assistant can describe what it read and provide result panels; original file bytes and exported app packages can be delivered as downloads rather than pasted into the transcript.

Read result panels

Tables show bounded result sets, so ask for the next page or a narrower filter when needed. Snippets and text previews can be shortened. Open the linked source or download when you need the complete original.

A file's contents are information for the task. Instructions written inside a document do not become authority to change workspace settings or send data elsewhere.

Import or extract

The Assistant can propose importing attached files into an app or starting document extraction. Read the card for the target app, selected files, and whether the action can be reversed. When an operation requires a person, follow its manual path.

Troubleshoot attachments

If upload fails, check the file size, connection, and displayed reason, then attach it again after resolving the cause. Do not send a request that assumes a failed attachment arrived. If processing starts but the reply is interrupted, inspect the destination app or extraction status before submitting another operation.