Creating a file

What a produced file is built from#

A document Connect writes is assembled from material it can point at: records in the workspace, a file you attached, Knowledge the workspace supplied, and the words of the request itself. Everything in the finished file traces back to one of those four.

That is a real constraint, and it shows. Ask for a quotation and Connect will lay out the document, carry across the customer, the items and the dates it can see, and leave the price as an obvious gap rather than a plausible number. The Assistant's authority is deliberately narrower than yours, and pricing is one of the things it does not hold — what the Assistant may not do sets out the rest.

Which formats it will write#

The writable formats are whatever file_formats can produce, and that list is narrower than the list of formats Connect can *read*. Asking for something outside it comes back as a refusal that names what is available, rather than a file with unexpected contents inside a familiar extension.

If you need a specific format for something downstream, say so in the request rather than renaming the file afterwards. A file whose extension disagrees with its bytes is exactly the thing validation exists to catch, and it will be caught the next time it is uploaded anywhere.

Creating a file is a change, so it is approved like one#

create_file is a writing tool. In the Assistant it arrives as a proposed action showing what will be produced, and nothing is written until you run it. Under an autonomy rule that requires a person, the proposal waits in Needs You with everything needed to judge it.

1. Say what the document is for, who it is for, and what must be in it.

   Result Connect resolves the record it names — the company, the deal, the case — instead of guessing from a name.

2. Read the proposal, including the fields it says it could not fill.

   Result You find out what is missing before the file exists, which is much cheaper than finding out after it has been sent.

3. Run it.

   Result The file is written to the workspace file store, an audit entry records the request and the tool, and the file appears on the Files sheet in the Data grid.

4. Link it to the record it belongs to, if that did not happen as part of the request.

   Result The document turns up on that company, deal or case for anyone who opens it later — see linking a file to a record.

Where it lands, and what it is not#

In the workspace file store

The same media_assets store an uploaded file goes to, scoped to your workspace and under row-level security. There is no second place for generated files.

As version 1

Every produced file starts a chain. The first change makes version 2 and the original stays readable — file versions explains what that buys you.

Not sent anywhere

Creating a document does not email it, attach it to a thread or share it outside the workspace. Sending is its own action under its own autonomy rule.

Not a knowledge source

A generated file does not start grounding future answers. Adding it to Knowledge is a separate decision, and usually the wrong one for a document Connect wrote.

Questions#

Related#

• Changing a file
• File versions
• Linking a file to a record
• Creating a document, end to end
• Proposed actions
• What the Assistant may not do