Short answer: You can create pandadoc document in PandaDoc by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the PandaDoc Create PandaDoc Document action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Document Name name | string | Required | – |
Template UUID template_uuid | string | Required | – |
Recipient Email recipient_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Recipient First Name recipient_first_name | string | Optional | – |
Recipient Last Name recipient_last_name | string | Optional | – |
Recipient Role recipient_role | string | Optional | – |
Tokens (JSON array) tokens_json | string | Optional | [{"name":"Client.Name","value":"Jane Doe"}] |
{"name": "{{trigger.name}}","template_uuid": "{{trigger.template_uuid}}","recipient_email": "e.g. user@example.com","recipient_first_name": "{{trigger.recipient_first_name}}","recipient_last_name": "{{trigger.recipient_last_name}}"}
{"id": "doc_abc","name": "Contract","status": "document.draft","date_created": "2026-05-11T00:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.