Send PandaDoc Document: PandaDoc action

Inputs

The fields this action accepts.

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	—

Sample request

{
  "document_id": "{{trigger.document_id}}",
  "subject": "e.g. Quick update",
  "message": "{{trigger.message}}",
  "silent": "{{trigger.silent}}"
}

Returns

{
  "id": "doc_abc",
  "status": "document.sent"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Send PandaDoc Document.

What does the Send PandaDoc Document action do in PandaDoc?

Transitions a draft to sent, triggering the per-recipient email. The standard "review complete → send to client for signature" workflow step.

What inputs does Send PandaDoc Document require?

Required: Document ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if PandaDoc returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send PandaDoc Document support batch operations?

Yes. Run Send PandaDoc Document inside a Loop node to process arrays. Tiny Command handles PandaDoc's rate limits automatically so you don't have to throttle manually.

More actions