Short answer: You can send pandadoc document in PandaDoc by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the PandaDoc Send PandaDoc Document action to a workflow, map its 4 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 ID document_id | string | Required | The Document ID assigned by Pandadoc. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Email Subject subject | string | Optional | Message subject line. |
Email Message message | string | Optional | – |
Silent (no email) silent | options | Optional | – |
{"document_id": "{{trigger.document_id}}","subject": "e.g. Quick update","message": "{{trigger.message}}","silent": "{{trigger.silent}}"}
{"id": "doc_abc","status": "document.sent"}
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.