build-gen-templatelisted

# Build a generation template > **PREREQUISITE:** Use the `propper` skill for authentication, tool routing, and the > agreement status model. Drafting the template body needs no account; saving it does. A template is the document with its variable parts pulled out into named fields. Getting those boundaries right is the whole job — everything downstream is mechanical. To fill a template that already exists, use `generate-document`. For a ready-made library of common agreements, use `agreement-starter-pack`. ## Steps ### 1. Authenticate `get_current_user`. Report the organization. Stop on failure per the `propper` skill. ### 2. Choose the engine | Source | `generationKind` | Notes | |---|---|---| | HTML, Markdown or MDX text | `HTML_MDX` | The default when omitted. Styling via `cssStyles`, `headerTemplate`, `footerTemplate` | | A Word `.docx` file | `DOCX_HANDLEBARS` | `templateContent` is the file bytes base64-encoded, 25MB before encoding | | A DocuSign Gen export | — | Not created here. Use `manage_gen_template` with `action` `import_from_source` | `DOCX_HANDLEBARS` needs the DOCX upload capability on the account. Without it the call returns `422 GENERATION_KIND_NOT_SUPPORTED_HERE`. Say that plainly rather than retrying. `SIGN_PDF_DOCGEN` cannot be created here at all; supplying it returns the same `422`. ### 3. Separate what varies from what does not Work from the actual document. A span is a field when it would differ between two real copies: - party names, e