Use “Generate paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Generate paid document
Use “Generate paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
Use Paid Document Fulfillment in Recued for transactional offer, paid workflow, form response, and payment. It includes 10 ready-to-run workflows and 4 related packs in one install.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Start paid document fulfillment” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Reconcile document payments against Stripe” in Recued. Owner-attended payment sweep - the manual safety net under the webhook observer.
Use “Reconcile a paid document refund” in Recued. Owner-attended refund close for one order.
Use “Inspect a paid document dispute” in Recued. Owner-attended read-only inspection binding one Stripe Dispute to one order.
Use “Review paid document artifacts” in Recued. It carries out the named workflow using the connections and settings you choose.
Show all 11 recipes
Use “Approve and deliver paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Reconcile paid document delivery” in Recued. Owner-attended mail-claim reconciliation for one order's two sends: the checkout-link mail (start) and the delivery mail (approve-deliver).
Use “Reject or cancel paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Reconcile and expire paid document fulfillments” in Recued. Manual order sweep.
Use “Close and archive a paid document fulfillment” in Recued. Owner-attended close for one order that never took money: draft, pricing, awaiting payment (verified unpaid at Stripe by a fresh read of its own session), or expired moves to cancelled. A session the provider reports paid refuses loudly - run the payment sweep instead.
This recipe forwards only full_name and project_summary from the accepted answer to static rendering and optional AI drafting. Templates may also use visitor.email, system.accepted_date, and ai.draft. Missing answer fields remain absent, so a template that uses one still fails strict rendering. To use another answer field, add its named read and projection to the response_named_values steps and declare it in metadata.requires_form_fields before saving the recipe. Unrelated visitor answers are not sent to the renderer or AI.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
submission id
setting
=
[object Object]
generation mode
setting
=
static
template file ref
setting
=
reference file ref
setting
=
reviewed artifact sha256
setting
=
Uses (10 operations)
core.seller.order.list
core.seller.order.transition
core.storage.data-file-read
core.data.form-response.get
recued-core.docling.document.to_markdown
core.ai.summarize
core.ai.generate
core.storage.file.render-markdown-template
recued-core.pandoc-pack.document.markdown_to_pdf
core.seller.order.attach-artifact
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
2 more aren't listed here. You'll see them at install.