Workflow origin for the PandaDoc document closure loop. It reads one document's status and details for context, sends that draft document through recued-core.pandadoc.document.send with owner-provided subject/message, and when the send succeeds it seeds durable data.shared closure state for pandadoc-document-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create documents, edit recipients, send reminders, configure auto-reminders or auto-expiration, open embedded sessions, configure webhooks, download files, delete, transfer ownership, or call arbitrary PandaDoc endpoints.
Send PandaDoc document with closure
Workflow origin for the PandaDoc document closure loop. It reads one document's status and details for context, sends that draft document through recued-core.pandadoc.document.send with owner-provided subject/message, and when the send succeeds it seeds durable data.shared closure state for pandadoc-document-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create documents, edit recipients, send reminders, configure auto-reminders or auto-expiration, open embedded sessions, configure webhooks, download files, delete, transfer ownership, or call arbitrary PandaDoc endpoints.
Complete workflow
PandaDoc Document Closure Loop
5 pinned recipes
Workflow pack for Recued-sent PandaDoc documents. It composes the PandaDoc capability pack with a closure ledger: send one draft or approved document through the existing PandaDoc approval gate, persist only the document/template linkage in data.shared, and let a scheduled watcher re-read that exact document until PandaDoc reports completion, exception, or an approval-complete state that needs the owner to send again. This pack does not duplicate PandaDoc auto reminders, manual reminders, auto-expiration, webhook administration, or general document status dashboards; it adds Recued-visible closure state for documents Recued sent.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Scheduled adopter for PandaDoc document closure rows seeded by send-pandadoc-document-with-closure. It lists only Recued-originated document watches, re-reads a bounded batch of document from PandaDoc, and closes the shared row when PandaDoc reports a terminal status or an approval-complete status that needs the owner to send again. It can notify the owner on completion or exception status, but it never sends documents, sends reminders, changes recipients, configures auto-reminders or auto-expiration, creates webhooks, downloads files, deletes documents, transfers ownership, or calls arbitrary PandaDoc endpoints.
Read-only PandaDoc document brief. It reads one document's status and detailed evidence through recued-core.pandadoc, then asks the AI summarizer for recipient state, approval/payment context, pricing and metadata signals, risks, and next steps. It never sends, downloads, deletes, creates sessions, edits recipients, moves folders, or mutates the document.
Low-frequency timeout role for recued-core/pandadoc-document-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Owner-visible list/close role for recued-core/pandadoc-document-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (35 steps)
document_id
trim
Trim whitespace from setting document id
subject
trim
Trim whitespace from setting subject
message
trim
Trim whitespace from setting message
reason
trim
Trim whitespace from setting reason
status
?
document
?
has_subject
compare
Check if subject has data
status_norm
lowercase
Convert status result status to lowercase
status_is_sendable
compare
Check if status norm is one of setting sendable statuses
skip_send
any
Check if any of the conditions are true
send
?
skip: step.skip_send equal true
sent_document_id
default
Apply default
has_sent_document
compare
Check if sent document id has data
requested_status
default
Apply default
template_id_primary
default
Apply default
template_id
default
Apply default
has_template
compare
Check if template id has data
sent_at
date_add
Add 0 days to
raw_document_key
default
Apply default
document_key_colon
replace
Replace text in raw document key
document_key_slash
replace
Replace text in document key colon
document_key_dot
replace
Replace text in document key slash
document_key_at
replace
Replace text in document key dot
document_key_space
replace
Replace text in document key at
document_key_left_angle
replace
Replace text in document key space
document_key_right_angle
replace
Replace text in document key left angle
document_key_plus
replace
Replace text in document key right angle
document_key_equals
replace
Replace text in document key plus
document_key_question
replace
Replace text in document key equals
skip_closure_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_pandadoc_closure_watch
?
skip: step.skip_closure_seed equal true
skip_template_link
any
Check if any of the conditions are true
link_document_to_template
?
skip: step.skip_template_link equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
reason
setting
=
silent
setting
=
false
message
setting
=
subject
setting
=
pandadoc
setting
=
document id
setting
=
sendable statuses
setting
=
document.draft,document.approved,draft,approved
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.