Import Procedures from an SOP

Import converts one supported SOP document into reviewable Procedure drafts. It is a drafting aid, not a publishing action and not a substitute for testing.

Supported input and limits#

Open Procedures, select Add, then Import. Choose a TXT, MD, HTML, PDF, DOCX, or EPUB file. The uploaded file may be at most 20 MB, and extracted text is capped at 300,000 characters. Empty, unsupported, oversized, or unextractable input is rejected before generation where possible.

The importer uses the model selected in the current agent draft and makes one forced model request with structured output. It can return a maximum of ten Procedure drafts. Every imported result is Free-form, not Structured. The generated ID, name, trigger, and content are validated before the results are returned.

What import changes#

Import creates drafts only. Existing Procedures stay unchanged, ID collisions are renamed safely, the first imported result is selected, and normal Agent Studio autosave stores the combined draft. Nothing is published automatically. Review every trigger and instruction, add any needed Tools or guardrails, then test before Publish.

Model usage for import counts toward the workspace quota and is recorded with the procedure_import purpose. A workspace without an active positive allowance is rejected before the model call.

Recover from failures#

If extraction fails, verify the format and that a scanned PDF contains selectable text. If the importer is temporarily unavailable or rate-limited, wait and retry; repeated clicks do not create a published version. If a result is too broad, edit the Free-form draft or rebuild it as a Structured Procedure manually.

Developers can call Import agent Procedures. The endpoint returns items and does not save or publish them for the caller.