The final stage of every workflow — taking the structured, reviewed data assembled upstream and converting it into deliverables. PDF generation, Conga CPQ, DocuSign e-signatures, email delivery, and Salesforce update blocks turn workflow output into proposals that go out the door.
Proposal blocks always follow a human gate. Best practice in RenderDraw workflows is to place a human review gate immediately before the first proposal block. The gate ensures that AI-drafted content, AI-extracted quantities, and ERP pricing have been reviewed and approved by a human before anything is delivered to the customer or submitted to a CPQ system.
Proposal sections drafted with context
Estimator reviews and approves
Render proposal from template
Push to CPQ for pricing finalization
Deliver to customer with PDF attached
Update opportunity stage and attach PDF
The PDF generation block renders a proposal PDF from a configured template, with all variable fields filled from workflow data. The template defines layout, branding, static content (company boilerplate), and placeholder fields (customer name, pricing tables, project scope, AI-drafted narrative sections).
Templates are HTML/CSS documents with Handlebars-style field injection — {{field_name}} for simple values, {{#each items}} ... {{/each}} for repeating sections like line item tables. Templates are version-controlled — updating a template does not affect in-flight workflow runs using the previous version.
<!-- Proposal header -->
<h1>{{project_name}}</h1>
<p>Prepared for: {{customer_name}}</p>
<p>Date: {{today_date}}</p>
<!-- Conditional bonding section -->
{{#if bonding_required}}
<section class="bonding">
<h2>Bonding Capacity</h2>
<p>{{company_bonding_statement}}</p>
</section>
{{/if}}
<!-- Line items table -->
<table>
{{#each line_items}}
<tr>
<td>{{description}}</td>
<td>{{quantity}} {{unit}}</td>
<td>{{unit_price}}</td>
<td>{{total_price}}</td>
</tr>
{{/each}}
</table>The Conga CPQ submit block pushes workflow-assembled quote data into Conga CPQ (Apttus CPQ) for pricing finalization, approval workflow, and CPQ-side document generation. It bridges RenderDraw's AI-powered extraction and drafting pipeline with the existing Conga CPQ workflow your sales team uses.
This block is designed for organizations that have Conga CPQ as their system of record for quotes but want to automate the upstream work of extracting scope, looking up pricing, and drafting proposal content before the quote enters Conga.
Conga approval workflow preserved. Submitting via the Conga CPQ block does not bypass Conga's internal approval workflow. If the quote total exceeds your configured Conga approval threshold, it will enter the Conga approval queue as normal. RenderDraw's human gate handles pre-submission review; Conga handles post-submission internal approval.
Conga Composer integration. The Conga CPQ submit block can optionally invoke a Conga Composer template after quote creation — generating a Conga-formatted proposal document and attaching it to the Salesforce opportunity as a ContentDocument. This replaces the manual "Generate Document" button click in Salesforce.
The DocuSign envelope block creates a DocuSign envelope from a generated PDF or from a DocuSign template, configures signer routing, and sends the envelope for signature. It handles the full envelope lifecycle — creation, sending, and status monitoring via a companion status poll block.
Pair the DocuSign envelope block with a DocuSign Connect webhook trigger to create a follow-on workflow that fires when all signers have completed. This "completion workflow" can:
For contracts requiring DocuSign. The DocuSign envelope block replaces the manual step of exporting the PDF, uploading to DocuSign, and configuring signers — saving 10–15 minutes per contract and eliminating the risk of attaching the wrong document or incorrect signer email.
The email delivery block sends a transactional email with the proposal PDF attached, a 3D viewer link embedded, or a DocuSign signing link included. It supports rich HTML email templates with workflow data injection, multiple recipients, CC/BCC, and delivery tracking.
Subject: Proposal — {{project_name}}
Dear {{customer_contact_name}},
Thank you for the opportunity to bid on {{project_name}}. Please find our proposal attached.
Our proposed approach includes:
Total proposed value: {{total_price_formatted}}
Please review the attached PDF and contact me with any questions.
Best regards,
{{account_manager_name}}
The Salesforce update block closes the loop — writing workflow results back into Salesforce after proposal delivery. Update the Opportunity stage, attach the generated PDF as a ContentDocument, log the workflow run ID as a custom field, and create an Activity record documenting the proposal submission.
StageName → "Proposal Submitted" (or your custom stage name)Proposal_Submitted_Date__c → workflow run timestampProposal_Value__c → total price from pricing blockRD_Workflow_Run_ID__c → workflow run ID for audit trail cross-referenceProposal_PDF_URL__c → download URL for the generated PDFFull-circle CRM hygiene. The combination of Salesforce Event Trigger (to start the workflow when an Opportunity reaches the bid stage) + Salesforce Update block (to update the Opportunity when the proposal is delivered) means your Salesforce pipeline stays accurate automatically — no manual stage updates, no forgotten attachments.
Every proposal block uses field mapping to connect workflow data to the target system — PDF template fields, Conga quote line fields, DocuSign signer email addresses, Salesforce record fields. Field mapping is configured visually in the block settings panel — no code required.
The mapping editor shows all available workflow data fields on the left (accumulated from all upstream blocks) and all available target fields on the right. Connect them by drawing lines between fields, or use the auto-map feature to automatically connect fields with matching names.
Where a simple field copy isn't enough — for example, you need to format a number as currency, concatenate first and last name, or compute a sum — the mapping editor supports inline transform expressions:
format_currency(total_price, "USD") → "$ 124,500.00"concat(first_name, " ", last_name) → "Jane Smith"sum(line_items, "total_price") → grand total numberformat_date(due_date, "MMMM D, YYYY") → "September 18, 2025"PDF templates and Conga templates both support conditional sections — blocks of content that appear only when a workflow condition is true. Configure conditions in the template using Handlebars conditionals ({{#if bonding_required}}) or in Conga using conditional line logic.
Common conditional sections:
From RFP receipt to signed proposal delivered — automated, reviewed, and recorded. Start with your most common proposal type.