<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>pandadoc &#8211; iAIFeed</title>
	<atom:link href="https://www.iaifeed.com/tag/pandadoc/feed" rel="self" type="application/rss+xml" />
	<link>https://www.iaifeed.com</link>
	<description>iAIFeed</description>
	<lastBuildDate>Thu, 22 Oct 2026 12:43:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://www.iaifeed.com/wp-content/uploads/2026/07/cropped-iaifeed1-80x80.png</url>
	<title>pandadoc &#8211; iAIFeed</title>
	<link>https://www.iaifeed.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Automate PandaDoc Proposals With the API and HubSpot</title>
		<link>https://www.iaifeed.com/how-to-automate-pandadoc-proposals-with-api</link>
					<comments>https://www.iaifeed.com/how-to-automate-pandadoc-proposals-with-api#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 12:43:44 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[pandadoc]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-automate-pandadoc-proposals-with-api</guid>

					<description><![CDATA[Auto-generate proposals from CRM deal data, sync signature status back, and stop copying fields by hand. Two working API calls and the limits that will bite at scale.]]></description>
										<content:encoded><![CDATA[<p>Automating <a href="https://www.iaifeed.com/ai-tool/pandadoc">PandaDoc</a> means one API call to create a document from a template with variables filled in, a second to send it, and a webhook to sync signature status back into your CRM. That removes the manual copy step that eats ten minutes per proposal.</p>
<p>The API is REST with per-document token auth, and the whole flow is roughly 40 lines of code. The complexity lives in choosing which fields are variables and which the rep must edit.</p>
<h2 id="what-can-the-pandadoc-api-actually-do">What Can the PandaDoc API Actually Do?</h2>
<p>The API covers: create document from template, send document, fetch status, download PDF, and configure webhooks. It does not let you design templates — that stays in the UI.</p>
<p>Endpoints you will use first:</p>
<ul>
<li><code>POST /public/v1/documents</code> — create from template with a <code>tokens</code> payload.</li>
<li><code>POST /public/v1/documents/{id}/send</code> — send to a recipient.</li>
<li><code>GET /public/v1/documents/{id}</code> — returns <code>status</code> as draft, sent, viewed, completed, or declined.</li>
</ul>
<p>Auth is an <code>API-Key</code> header, generated under <strong>Settings → API</strong>. Keys are per workspace, not per user, so rotate them when someone with access leaves.</p>
<h2 id="how-do-i-create-a-document-from-deal-data">How Do I Create a Document From Deal Data?</h2>
<p>Map CRM fields to template tokens. A token in the template looks like <code>[client.name]</code>, and the API call sends it by name.</p>
<pre><code class="language-json">POST /public/v1/documents
{
  &quot;name&quot;: &quot;Proposal - Acme&quot;,
  &quot;template_uuid&quot;: &quot;YOUR_TEMPLATE_UUID&quot;,
  &quot;recipients&quot;: [{&quot;email&quot;: &quot;buyer@acme.com&quot;, &quot;role&quot;: &quot;Client&quot;, &quot;first_name&quot;: &quot;Dana&quot;}],
  &quot;tokens&quot;: [
    {&quot;name&quot;: &quot;client.name&quot;, &quot;value&quot;: &quot;Acme Inc&quot;},
    {&quot;name&quot;: &quot;deal.amount&quot;, &quot;value&quot;: &quot;45000&quot;}
  ]
}
</code></pre>
<p>Keep the token list short. Every token you add is a field someone has to keep populated in the CRM; unused tokens render as empty space in the sent document.</p>
<h2 id="how-do-i-sync-signature-status-back-to-hubspot">How Do I Sync Signature Status Back to HubSpot?</h2>
<p>Use a webhook, not polling. Register it under <strong>Settings → Integrations → API → Webhooks</strong> pointing at your endpoint, and subscribe to <code>document.completed</code>.</p>
<p>On receipt, look up the deal by the <code>metadata</code> you attached at creation time — pass your deal ID as metadata so you do not have to match on document name. Then update the deal stage.</p>
<table>
<thead>
<tr>
<th>Event</th>
<th>Typical CRM action</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>document.sent</code></td>
<td>Move deal to Proposal Sent</td>
</tr>
<tr>
<td><code>document.viewed</code></td>
<td>Log activity, notify rep</td>
</tr>
<tr>
<td><code>document.completed</code></td>
<td>Move to Closed Won, attach PDF</td>
</tr>
<tr>
<td><code>document.declined</code></td>
<td>Reopen, add note</td>
</tr>
</tbody>
</table>
<p>Polling the API instead of using webhooks gets rate-limited within a day on an active sales team. There is no reason to do it.</p>
<h2 id="what-are-the-rate-limits-and-gotchas">What Are the Rate Limits and Gotchas?</h2>
<p>PandaDoc limits API requests to roughly 100 per minute per workspace on standard plans. That is generous for proposal creation and tight if you bulk-generate 500 documents — batch with a delay rather than firing a loop.</p>
<p>Three gotchas worth knowing:</p>
<ol>
<li>A document created with a template must be sent, never edited, or the rep loses the ability to change it in the UI.</li>
<li>Tokens with the same name across template versions collide; version your templates and pin the UUID.</li>
<li>PDF downloads are metered separately and count against your plan&#8217;s document limit on lower tiers. Generating test PDFs repeatedly burns quota.</li>
</ol>
<h2 id="is-the-api-available-on-the-cheapest-plan">Is the API Available on the Cheapest Plan?</h2>
<p>The API is on every paid plan including Starter at $19 per user per month, but webhooks are effectively a Business feature in practice because the approval workflow they trigger lives there. Check your plan before designing an automation around approvals.</p>
<h2 id="who-should-not-automate-this">Who Should Not Automate This?</h2>
<p>If your reps send fewer than ten proposals a month, the automation costs more to build and maintain than the manual work it replaces. Proposals also carry nuance — a rep editing the summary paragraph often wins the deal. Automate the data, leave the narrative editable.</p>
<h2 id="quick-summary">Quick Summary</h2>
<ul>
<li>Two API calls create and send a proposal; a webhook syncs status back.</li>
<li>Pass your CRM deal ID as document metadata so status updates can match reliably.</li>
<li>Rate limit is about 100 requests per minute per workspace.</li>
<li>Never edit a document after creating it via the API — send it instead.</li>
<li>Only worth automating above roughly ten proposals a month.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-automate-pandadoc-proposals-with-api/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Create and Send Your First PandaDoc Proposal in 2026</title>
		<link>https://www.iaifeed.com/how-to-create-and-send-a-pandadoc-proposal</link>
					<comments>https://www.iaifeed.com/how-to-create-and-send-a-pandadoc-proposal#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 12:43:27 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[pandadoc]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-create-and-send-a-pandadoc-proposal</guid>

					<description><![CDATA[Build a reusable template, add pricing tables and signature blocks, then send a tracked proposal. Covers the 14-day trial, per-seat pricing and why templates fail on import.]]></description>
										<content:encoded><![CDATA[<p>A <a href="https://www.iaifeed.com/ai-tool/pandadoc">PandaDoc</a> proposal is a PDF-like document you edit in the browser, with drag-and-drop pricing tables and legally binding signature fields. The fastest path is: upload a template, place fields, insert a pricing table, then send it and watch the view log.</p>
<p>Most people get value in the first 15 minutes and then stall on templates. That stall is worth understanding before you commit a team to the tool.</p>
<h2 id="what-is-pandadoc-and-who-is-it-for">What Is PandaDoc and Who Is It For?</h2>
<p>PandaDoc is a document automation platform for proposals, quotes, and contracts. Its differentiator is the pricing table with optional line items and approval logic — the buyer can select a tier and the total recalculates inside the document.</p>
<p>It is built for sales teams sending 20+ documents a month. A freelancer sending one proposal a week should compare it against a free Google Doc with a signature add-on before paying per seat.</p>
<h2 id="how-do-i-create-a-proposal-from-scratch">How Do I Create a Proposal From Scratch?</h2>
<ol>
<li>Log in and click <strong>New → Document</strong>.</li>
<li>Choose a template from the library, or start blank and upload a <code>.docx</code>. Import preserves headings and paragraphs but flattens complex layouts — tables and text boxes usually break.</li>
<li>Add content blocks on the left rail: text, image, pricing table, video, or a Q&amp;A section.</li>
<li>Drag fields from the right rail onto the page: Signature, Initials, Date Signed, Text Field, Dropdown.</li>
</ol>
<p>Assign a role to each field (Client, Sales Rep). Roles are what let one template serve both parties without duplication.</p>
<h2 id="how-do-i-build-a-pricing-table-that-actually-works">How Do I Build a Pricing Table That Actually Works?</h2>
<p>Pricing tables are where PandaDoc earns or loses the buyer in the first scroll.</p>
<ul>
<li>Use the <strong>Pricing Table</strong> block, not a pasted table. Pasted tables do not compute totals.</li>
<li>Add optional items only for genuine upsells; more than three options delays decisions.</li>
<li>Set a currency per document, not per line — mixed currency tables confuse buyers and break discounts.</li>
<li>Attach an approval workflow if a discount exceeds a threshold; that is a Catalog setting, done under <strong>Settings → Approvals</strong>.</li>
</ul>
<h2 id="how-do-i-send-it-and-know-if-it-was-read">How Do I Send It and Know If It Was Read?</h2>
<p>Click <strong>Send</strong>. You can require the recipient to view before signing, which builds a stronger audit trail than a plain email attachment.</p>
<p>After sending, the document page shows a timeline: sent, viewed, time spent per page, signed. That view data is the reason sales teams pay for PandaDoc — a proposal read three times on page 4 tells you the pricing table is the sticking point.</p>
<p>Enable reminders on the send dialog. One reminder after 48 hours lifts response rates noticeably, and nobody sends it manually.</p>
<h2 id="how-much-does-pandadoc-cost">How Much Does PandaDoc Cost?</h2>
<p>There is a 14-day free trial, no card required, and it limits you to a handful of documents. Paid plans start at $19 per user per month billed annually for the Starter tier, which includes unlimited e-signatures but caps templates.</p>
<p>The Business tier at $49 per user per month is the one most teams actually need, because template locking and approval workflows sit there. Per-seat billing is the trap: a five-person sales team on Business is roughly $2,940 a year, which is more than a small CRM.</p>
<h2 id="why-do-templates-break-on-import">Why Do Templates Break on Import?</h2>
<p>Word import handles text, headings, and simple lists. It does not handle nested tables, text wrapped around images, multi-column layouts, or embedded footnotes. Those arrive as overlapping boxes you end up rebuilding by hand.</p>
<p>Practical fix: rebuild the layout in PandaDoc natively once, then reuse the digital template. Do not maintain a Word master and re-import it every quarter — that cycle burns an afternoon each time.</p>
<h2 id="who-should-skip-pandadoc">Who Should Skip PandaDoc?</h2>
<p>Skip it if your proposals never contain pricing options, if one person sends all documents, or if you are already paying for a CRM with native quote generation. PandaDoc&#8217;s real value is the pricing table plus the approval chain, and neither matters for a single-sender business.</p>
<h2 id="quick-summary">Quick Summary</h2>
<ul>
<li>PandaDoc proposals combine editable content, pricing tables and e-signatures in one document.</li>
<li>Build templates in PandaDoc natively; Word import breaks complex layouts.</li>
<li>Pricing tables must use the native block or totals will not compute.</li>
<li>The 14-day trial is card-free; Business tier at $49/user/month unlocks approvals.</li>
<li>Per-seat pricing is heavy for teams under three users.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-create-and-send-a-pandadoc-proposal/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
