Skip to main content

Make a file from documentation

Upload your receiving system's documentation and we propose the file for you to check.

Upload the documentation

Open the flow, go to the We send step, and select Make another file. Under Need a set layout?, select From documentation. Drop the documentation on the upload area, or choose it.

We read the documentation, which can take a moment, and open a Check the values form. Nothing is saved yet.

If this fails

The screen says why. For example "We couldn't read the documentation. Try again.", or that this workspace has used its monthly AI allowance, or keeps documents on our own servers so nothing can be sent to AI. If you do not see From documentation, this is not switched on for your workspace.

Check the format

We propose a file type: CSV, JSON, XML or fixed-width text. Under it, a line shows where the documentation says so, with the page of a PDF or the line of another file, and a short quote. If we could not find the place, the form says: "We couldn't find where the documentation says this."

You know which file type is proposed, and you can see why.

Check every value

Each row of the proposed file shows the field of your flow that we chose for it, with the place in the documentation it came from. A row marked Required is one the documentation says must be present.

Change any row with its Value list. For fixed-width text, check the width of each row too.

If the documentation is long, we read only its first 150,000 characters, and the form says so. Check that nothing you need is missing. Parts of the proposal we could not use are left out, and the form says that too.

Every row has the field you want, or Not set if it should carry no value.

Add a destination if the documentation names one

If the documentation says where to send the file, the form says "The documentation says to send to" and gives the address and the method. Select Add this destination to open the destination form with those details filled in. We never create it for you. You still enter the sign-in yourself. See Destination sign-in, keys and signing.

Or choose Download only, or a destination you already have, in Send to.

The file knows where it goes.

Send a test, then create

When the file goes to a destination, Send a test must pass before Create works. The test sends a real file made from a document in this flow, with TEST_ at the start of its name. That file holds that document's values, so use a destination you trust. If the flow has no document yet, upload one first.

Change anything in the form and the test must be sent again, because it only counts for exactly what you are about to create. A test that fails shows the destination's message.

Select Create. Nothing is created until you do. To start again with other documentation, select Choose a different file.

The file is saved, and its editor opens, where you can add lookups and send-when rules. See Make a file.

What we send to AI

The text of your documentation and the keys, labels and types of your flow's fields. No document or its values. The result is a proposal and is never applied by itself. See AI in ProcuLink.