signvoy_create_document
Create a new signing document (in 'draft' state) from a published template. PREREQUISITE: call signvoy_get_template first to retrieve the recipient role keys — each entry in 'recipients' must match a roleKey from the template. Call signvoy_send_document afterwards to email recipients. Keep create and send separate so a human can review the draft before real emails go to counterparties.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"template_id": "<template_id>",
"recipients": "<recipients>"
},
"name": "signvoy_create_document"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Document title. Defaults to the template name. | |
| message | No | Optional personal message included in the signing invitation email. | |
| recipients | Yes | Everyone involved, in signing order. One entry per template recipient role, plus any 'cc' or 'viewer' entries. At least one must sign or view. | |
| expiry_days | No | Days after sending that the document can still be signed. Defaults to the template's deadline. The countdown starts when the document is sent, not when it is created. | |
| template_id | Yes | Published template UUID. Get from signvoy_list_templates (hasPublishedVersion must be true). | |
| workspace_id | No | Target workspace UUID. Safe to omit only when the user belongs to exactly one workspace; required otherwise, and omitting it then fails with the list of candidates. Call signvoy_list_workspaces to find it. | |
| email_subject | No | Replaces the generated subject line on the signing request and reminders. Completion, decline and cancellation notices always keep their standard wording. Omit to use the generated subject. |