--- title: "PandaDoc monday.com Integration: The Complete Setup Guide" description: "How to set up the PandaDoc monday.com integration properly: installing the app from the marketplace, mapping item columns to variables, handling pricing without line-item transfer, creating documents from the item, and the failure points to avoid." canonical: https://pureproposals.com/pandadoc-monday-integration-setup-guide/ published: 2026-10-07 image: https://pureproposals.com/images/blog/pandadoc-monday-integration-setup-guide/0.png site: Pure Proposals type: article --- # PandaDoc monday.com Integration: The Complete Setup Guide > How to set up the PandaDoc monday.com integration properly: installing the app from the marketplace, mapping item columns to variables, handling pricing without line-item transfer, creating documents from the item, and the failure points to avoid. _Source of truth: https://pureproposals.com/pandadoc-monday-integration-setup-guide/_ To set up the PandaDoc monday.com integration, install the PandaDoc app from the monday.com Apps marketplace, add the PandaDoc widget as a view on the board or item, sign in with your PandaDoc credentials, and integrate at the item level so your board's columns become document variables. The install takes minutes; making it a working system takes deliberate column mapping, templates built around those variables, and an honest plan for pricing, because monday.com line items do not flow into PandaDoc pricing tables the way CRM products do. That last point is the single most important thing to know before you start, and most setup advice skips it. Across the 129 sales calls we analysed, manual document creation was the top pain in 82 of them, and the teams suffering most usually had their tools connected already. The software was linked. The system was not. This guide covers both: the click-path to a clean install, and the decisions that separate "the widget is on the board" from "the team generates accurate, on-brand documents from the item in minutes." ## Key takeaways - The integration runs as a monday.com app: install it from the Apps marketplace, add the PandaDoc widget as a view, and sign in. It requires a PandaDoc Business or Enterprise plan. - Integrate at the **item level**, not the board level. Board-level integration maps only the item name; item-level integration maps every non-formula column as a document variable. - Formula columns and subitems cannot be mapped, and line items do not transfer into pricing tables or quote builder blocks. Pricing lives in PandaDoc's own catalog and tables, fed by your templates, not by the board. - Documents are created, sent, and tracked from the PandaDoc widget on the item, from templates or uploaded files, and the Related documents section shows each document's live status. - The monday.com desktop app does not support the integration, and variable mapping reads from the current board only. Plan board structure accordingly. - Test on real items, not test rows, and close the old Word or PDF route on a named date. An integration that runs in parallel with the old way loses to the old way. ## What the PandaDoc monday.com integration actually does Once installed, the integration does three jobs: 1. **Board data into documents.** Values from an item's columns populate PandaDoc variables, so a proposal opens pre-filled with the client name, project scope, dates, and totals exactly as they sit on the board. Template roles can also prefill recipient details, so the right contact is attached without retyping. 2. **Documents from the item.** The PandaDoc widget lives as a view on the board or item. From it, your team creates a document from a template (or uploads a PDF or Docx and drops signature fields on it), assigns recipients, and sends, without leaving monday.com. 3. **Status on the record.** The widget's Related documents section lists every document created from that item with its name, status, and creation time, so whoever owns the item can see at a glance whether the proposal is drafted, sent, viewed, or completed. Notice what is not on that list: automatic line-item transfer into pricing tables, and document status driving column values or monday automations out of the box. Those gaps are where configuration decisions matter most, and we cover both below. A partial integration is what produces the workaround culture where someone re-types board data into documents every few days: the pattern we call the human Zapier. The setup below makes that job not exist. ## Before you install: prerequisites and decisions Check the account requirements first: - **PandaDoc plan.** The monday.com integration is available on PandaDoc's Business and Enterprise plans. Check your plan before scheduling the rollout. - **Browser, not desktop app.** The monday.com desktop application does not support the PandaDoc add-on, so the team uses monday.com in the browser for document work. Pop-ups and redirects need to be enabled, and third-party cookies allowed, or the widget's sign-in will not stick. - **Workspace alignment.** PandaDoc supports multiple workspaces, but the widget shows documents from the workspace you are signed in to. Decide which PandaDoc workspace owns this board's documents before anyone connects. Then make two decisions that are much cheaper to make now than after rollout: - **Which board is the system of record?** Variable mapping reads from the current board only. If client data is scattered across a leads board, a projects board, and a finance board, pick the one board where documents will be generated and make sure it holds the columns your proposals need. - **Which columns will feed the documents?** Walk through your most-sent proposal and list every value in it that exists on the board. That list, not the full column set, is your variable scope. This is the same scoping discipline that a full [PandaDoc implementation](/pandadoc-implementation/) starts with, and skipping it is the number one reason integrations stall. ## Step 1: Install the PandaDoc app and add the widget In monday.com, open the Apps marketplace, find the PandaDoc app, and select Install app, choosing the workspace and board it should live on. Then add the widget where the team will use it: on the board or item, click Add view, pick Apps, search for PandaDoc, and add it. Sign in with your PandaDoc credentials. Once added, open an item and check the PandaDoc view loads and shows the Create new document control. If it does not, the usual causes are browser-side: blocked pop-ups, blocked third-party cookies, or the desktop app instead of the browser. Resolve that before going further; a half-working widget produces behaviour later that looks like mapping problems but is not. ## Step 2: Integrate at the item level and map columns to variables The integration works at two levels, and the choice decides how useful it is: - **Board level** maps only the Name variable. That is enough to label a document and nothing more. - **Item level**, the recommended setup, maps all non-formula columns on the board as variables. Choose item level. From a task item, the gear icon's View Tokens/Variables option shows every available variable in square brackets, which is exactly the list you place into templates. Two mapping rules to respect: - **Formula columns do not map.** If a value your documents need is computed by a formula column (a calculated total, a derived date), it cannot feed a variable directly. Either restructure so the value lands in a regular column, or accept that it will be entered in the document. - **Subitems do not map.** Data living on subitems is invisible to the integration. If your proposals need per-line detail that currently sits in subitems, that detail has to move up to the item or live in PandaDoc instead. For every variable you plan to use, check the column is **reliably populated** on real items before the stage where the team creates documents. A variable mapped to a usually-empty column is worse than none, because it produces blanks that make the team distrust generation entirely. Where a column is often empty, fix the process rather than the template: make filling it part of an earlier board stage, or drop the variable. A template with 10 dependable variables beats one with 30 theoretical ones. ## Step 3: Build templates around monday.com variables With the variable list settled, build the templates that consume it. In PandaDoc templates, place the square-bracket variables where the dynamic values belong: client and company names in the cover and agreement text, dates and scope fields in the body, totals in the summary. Date variables follow local time zone settings, so sanity-check how dates render for a team spread across regions. Assign template roles for recipients. Roles can prefill contact details like first name, last name, email, and phone from the people connected to the item, which removes the most error-prone retyping of all: the client's own details. The templates themselves deserve the same rigour as the mapping: locked branding, reusable library sections, one master template per document type rather than a folder of near-duplicates. Off-brand documents were a stated pain in 44 of the 129 calls we analysed, and an integration that fills ugly templates faster just produces ugly documents faster. That discipline is its own project, covered on our [PandaDoc templates](/pandadoc-services/pandadoc-templates/) service page. ## Step 4: Handle pricing honestly: line items do not transfer Here is the difference between this integration and PandaDoc's CRM integrations, and the thing to plan around: **monday.com line items cannot be pulled into a pricing table or a quote builder block.** With Pipedrive or HubSpot, products attached to the deal flow into the pricing table with quantities and prices intact. With monday.com, they do not. That is not a reason to abandon the integration. It is a reason to put pricing where it works: - **Keep the catalog in PandaDoc.** Build your products, prices, and SKUs in PandaDoc's catalog, and have pricing tables in the template pull from it. The team picks line items inside the document, from governed prices, instead of typing them. - **Use variables for totals and terms.** A contract value, a monthly fee, or a term length held in a regular board column maps fine as a variable into body text and summary sections. The itemised table is built in PandaDoc; the headline numbers can still come from the board. - **Step up to CPQ when rules enter the picture.** If pricing involves bundles, conditional options, volume discounts, or approval-gated margins, a flat table is not enough regardless of integration. That is [PandaDoc CPQ](/pandadoc-services/pandadoc-cpq/) territory, and it runs entirely inside PandaDoc, so the monday.com gap stops mattering. What you should not do is let the gap push pricing into a spreadsheet that gets pasted into documents: that reintroduces the typos, stale prices, and ungoverned discounts the integration was meant to remove. Our [pricing tables guide](/pandadoc-pricing-tables-complete-guide/) covers how to structure the tables themselves. ## Step 5: Create, send, and track documents from the item With templates and pricing settled, the team flow is short: open the item, open the PandaDoc view, and click Create new document. Pick the template (or bundle several), confirm the recipients the roles have prefilled, and the variables populate from the item's columns. The document opens in a modal or a new tab, gets its final line items picked from the catalog, and goes out. For one-off paperwork that does not justify a template, the widget's Upload tab takes a PDF or Docx, lets you drop signature and fillable fields on it, and sends it from the same place. Treat it as the exception: untemplated documents are where branding and pricing discipline quietly leak away. Tracking lives in the widget's Related documents section. At item level it lists that item's documents with live status; at board level it lists documents across the board and its items. That visibility is the integration's writeback story: status shows on the record, but it does not change column values or fire monday automations by itself. If you need document status to move a status column or advance a workflow, that is additional wiring beyond the native widget, worth scoping deliberately rather than assuming it exists. Until then, make the Related documents panel part of the team's routine: the answer to "has it been signed?" is on the item, not in someone's inbox. Teams we work with typically start at 45 to 50 minutes per proposal and get to minutes once generation runs from the record they already manage work in. ## Step 6: Test on real items, then cut over Test with live data before rollout: - Generate documents from five to ten real items, including at least one messy one: long scope text, an unusual character in a company name, a date column in another format. - Check every variable filled, the recipient details prefilled from the item's people, and the status appeared in Related documents within a minute of each change. - Have one team member, not the admin who built it, run the flow end to end in the browser and note every point of hesitation, including whether their pop-up and cookie settings let the widget sign in. Then roll out deliberately: short role-based training, a first-week target of every user sending at least one real document through the new flow, and a named date when the old route (Word, PowerPoint, duplicated PDFs) is closed. Teams that run old and new in parallel indefinitely drift back to the old way, because habit always wins a tie. The full playbook for this stage is in our [PandaDoc onboarding](/pandadoc-services/pandadoc-onboarding/) service. ## The four ways monday.com PandaDoc setups fail Having rescued a fair number of stalled setups, the failure points are consistent: 1. **Board-level integration left in place.** The widget was added at board level, only the name variable maps, documents generate nearly empty, and the team concludes the integration "doesn't really do anything." Re-integrate at item level and the variable list appears. 2. **Mapped-but-empty columns.** The variables exist, the data does not, documents generate with blanks, and the team goes back to typing. Fix the column discipline on the board or drop the variable. 3. **Pricing pushed back outside the system.** Because line items do not transfer, someone decides pricing belongs in a spreadsheet again, and every document inherits its errors. The catalog-in-PandaDoc pattern above exists so this gap does not become a regression. 4. **Formula and subitem data assumed in.** The proposal needs a computed total or per-line subitem detail, nobody checked that neither maps, and the gap surfaces mid-rollout as "the integration is broken." It is not broken; that data needed restructuring first. If you recognise your own setup in that list, the repair is usually faster than the original build, because the workarounds show you exactly what is broken. ## PandaDoc monday.com integration FAQ ### How long does the PandaDoc monday.com integration take to set up? The app install and widget setup take minutes. A working system with item-level mapping, dependable variables, tested templates, and a pricing catalog typically takes 2 to 5 days for a standard board. Column restructuring (moving needed values out of formula columns and subitems) and catalog build drive most of the timeline, not the technical install. ### What PandaDoc plan do I need for the monday.com integration? PandaDoc's Business or Enterprise plan. Check PandaDoc's current pricing page before committing, as plan packaging changes. ### Can monday.com line items flow into PandaDoc pricing tables? No. Line items cannot be pulled into a pricing table or a quote builder block, and subitems and formula columns cannot be mapped as variables. Build pricing in PandaDoc's catalog and pricing tables instead, and feed headline numbers like contract totals from regular board columns as variables. ### Why are my document variables coming through blank? Three usual causes, in order: the integration was added at board level, which maps only the item name (re-integrate at item level); the mapped column is empty on the item you generated from; or the value lives in a formula column or subitem, which the integration cannot read. Mapping also reads from the current board only, so values on other boards do not carry. ### Does document status write back to the monday.com item? Status is visible on the item: the widget's Related documents section shows each document with its live status, from draft through completed. The native integration does not change column values or trigger monday automations from document status, so if you need that, scope it as additional wiring rather than assuming it is included. ## Get the integration implemented properly The marketplace install gets you a widget. The [PandaDoc monday.com integration](/pandadoc-integrations/monday-com/) page covers what we build on top of it: item-level mapping that fills reliably, templates your team cannot break, a pricing catalog that closes the line-item gap, and a rollout the team sticks with. If your integration has been "set up" for months and documents are still assembled by hand, that gap is precisely what we fix.