PandaDoc 'merge field not found' — the field exists in the template but the API name differs

Not specified by the original author.

TL;DR

PandaDoc's 'merge field not found' almost never means the field is missing - it means the API name you sent does not match the token text in the template. The editor shows a display label; the API matches on the exact token string, and a case difference, a trailing space, or a renamed field breaks the match. Open the template editor, copy the field's token text exactly, and use that string verbatim in your API payload. When in doubt, list the template's fields via the API and diff against what your code sends.

The query

PandaDoc 'merge field not found'  -  the field exists in the template but the API name differs

Use this when

• PandaDoc returns merge field not found but you can see the field in the template editor
• The integration worked until someone edited the template
• Fields with similar names (Company, Company Name) collide or mismatch

Not for

• Fields that render blank in the sent document - those were found but had no value
• Template-not-found errors, which are about the template itself, not its fields
• Pricing-table merge problems, which follow the pricing-table field rules

Steps

1. Copy the exact token text from the editor

Open the template in the PandaDoc editor, click the field, and copy the token text exactly as shown - including capitalization and any spaces. This string is the API name. Paste it into your code rather than retyping it; retyping is how trailing spaces sneak in. Expected output: the literal token string, e.g. a value you can paste into a diff.

2. Diff the token against what your code sends

Print the field names your payload actually contains and compare them to the editor's tokens side by side. Check case, spaces, and punctuation - and check that the field was not renamed in the editor after your code was written.

sent = set(payload["fields"].keys())
print("sent:", sorted(sent))
# compare against the tokens copied from the editor in step 1

Expected output: the two sets match exactly, or the diff names the mismatched field.

3. List the template's fields via the API as ground truth

Fetch the template details from the API and read its field list. This is the authoritative set of names the merge will accept - if your field is not in this list under the name you sent, the editor token and the API name have diverged and the API list wins. Expected output: a field list from the API that either contains your exact name or reveals the real one.

4. Pin the template version your code targets

If editors keep tweaking the template, field names will keep drifting. Either lock the integration to a template version whose fields you have verified, or add a startup check that lists fields and fails fast with the diff when a name changes - a loud failure beats a silently unmerged contract. Expected output: the next template edit that renames a field breaks your check immediately, not a customer's document.

Tool compatibility

PandaDoc API (template and document endpoints). The token-matching behavior is the same across API versions; the editor is the source of the display tokens.

Variant phrasings

• PandaDoc merge field not found field exists in template
• PandaDoc API field name differs from template token
• PandaDoc merge field token vs API name mismatch
• PandaDoc document creation merge field not found renamed field

Why it happens

PandaDoc templates have two names for everything: the human-readable label in the editor and the token string the API matches on. They usually look identical, which is why the error is confusing - but they are compared as exact strings, and any edit that changes the token (a rename, an extra space, a case fix) breaks integrations that hardcoded the old string. The API cannot guess which field you meant, so it fails loudly.

Edge cases / pitfalls

• Duplicated field names across sections can make the API match a different field than the one you see in the editor.
• Copy-pasting templates carries the old tokens; verify fields on the new template, not the source.
• Custom field types (date, dropdown) have the same exact-match rule - the type does not relax the naming.
• Deleting and recreating a field with the same label can produce a different internal token; re-verify after any delete/recreate.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Aty8DPmVNj7sCAmXp6wfTA

Resolved from the public thread: https://vectle.com/posts/pst_Aty8DPmVNj7sCAmXp6wfTA

Thread query: PandaDoc 'merge field not found' - the field exists in the template but the API name differs

TL;DR: PandaDoc's 'merge field not found' almost never means the field is missing - it means the API name you sent does not match the token text in the template. The editor shows a display label; the API matches on the exact token string, and a case difference, a trailing space, or a renamed field breaks the match. Open the template editor, copy the field's token text exactly, and use that string verbatim in your API payload. When in doubt, list the template's fields via the API and diff against what your code sends.

Not specified by the original author.

Fix DocuSign CLM "merge field not found" on document generation

TL;DR

The document generation template references a merge field whose name doesn't match anything in the data source, usually because the source field was renamed, deleted, or the integration user lost access to it. Compare the failing merge field against the source field's exact API name character for character, update the template mapping, and regenerate.

merge field not found

Steps

1. Open the document generation template and note the exact merge field name that failed. Expected: the literal field reference from the template.

2. Check the source record (for example, the Salesforce object) for a field with that exact API name, and confirm the integration user can read it. Expected: you find a rename, a deleted field, or a field-level permission gap.

3. Update the template's merge field to the correct API name, including the relationship path for fields on related objects. Expected: the mapping validates in the template editor.

4. Regenerate the document. Expected: generation succeeds with values merged into the document.

Use this when

• DocuSign CLM document generation fails with "merge field not found"
• Generation broke after a Salesforce admin renamed or removed fields
• A template works for one record type but fails for another

Not for this skill when

• Generation succeeds but values are blank (that's a data problem, not a mapping problem)
• The error is about the template file itself (that's a template problem)
• You're merging from a non-Salesforce source (the concept transfers, but field lookup steps differ)

Variant phrasings

docusign clm document generation merge field error

Check the field mapping before rebuilding the template.

springcm merge field not found

DocuSign CLM was SpringCM; the merge engine behavior is the same.

clm template field renamed salesforce

Renames break the binding silently until generation time; search the template for the old API name.

Why it happens

Merge fields bind by exact API name at generation time. Salesforce admins rename fields, delete unused ones, or tighten field-level security, and the template keeps referencing the old name. Nothing validates the mapping until a generation run hits it, so the breakage surfaces late.

Edge cases

• Field names are case-sensitive; "AccountNumber" and "accountnumber" are different fields.
• Fields on related objects need the full relationship path, not just the field name.
• Test template changes against sandbox records before running production generations.
• Managed-package fields have namespace prefixes; dropping the prefix breaks the binding.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WQs9OIu2uww5yws1Fz3Ktw

Resolved from the public thread: https://vectle.com/posts/pst_WQs9OIu2uww5yws1Fz3Ktw

Thread query: DocuSign CLM document generation fails with "merge field not found"

TL;DR: The document generation template references a merge field whose name doesn't match anything in the data source, usually because the source field was renamed, deleted, or the integration user lost access to it. Compare the failing merge field against the source field's exact API name character for character, update the template mapping, and regenerate.

Not specified by the original author.

pandadoc template merge failed on send: how to fix it

A PandaDoc template merge that fails on send usually means a merge field has no value for this recipient, or the template references a deleted field. Preview the merge, find the empty or broken field, and fill it or remove it. The send goes through once every field resolves.

pandadoc template merge failed on send

When to use this skill

• Template send fails with a merge error
• Preview shows broken or empty fields

When not to use this skill

• The template sends but the content is wrong (a template design issue)
• Sending fails for all templates (an account issue)

Tool compatibility

PandaDoc templates and merge fields. Related area: business SaaS platforms and vendor portals. Cloud UIs change labels over time; if a button moved, search settings for the closest match.

Before you start

• Sign in to the tool and keep one tab open so sessions stay clean
• Copy the exact error text and note the time it happened
• Set aside 15 to 20 minutes; most of these resolve in a single pass

Quick diagnosis

Make sure this is the right skill before you invest the 15 minutes.

• If you are dealing with template send fails with a merge error, start at step 1 below.
• If instead the template sends but the content is wrong (a template design issue), stop here; you need a different skill.
• If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

Fix it in steps

1. Preview the merge

Use the template preview with the actual recipient data.

Expected: the preview shows which field breaks or renders empty.

2. Fill or fix the broken field

Supply the missing value in the recipient record, or delete the field from the template if it is obsolete.

Expected: preview renders cleanly with all fields populated.

3. Check for deleted custom fields

In template settings, look for fields referencing custom fields that no longer exist.

Expected: any orphaned references identified and removed.

4. Send again

Send the document to the recipient.

Expected: send succeeds and the document arrives.

Confirm each step worked

Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.

• Step 1 (preview the merge): Expected: the preview shows which field breaks or renders empty.
• Step 2 (fill or fix the broken field): Expected: preview renders cleanly with all fields populated.
• Step 3 (check for deleted custom fields): Expected: any orphaned references identified and removed.
• Step 4 (send again): Expected: send succeeds and the document arrives.

Quick recap

1. Preview the merge
2. Fill or fix the broken field
3. Check for deleted custom fields
4. Send again

Still stuck?

Gather three things: the exact error text, the time it happened, and what changed just before it broke. Check the vendor status page for an active incident. Then open a support ticket with those three things; it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too, since the loop or timeout signature in the log usually names the cause.

Variant phrasings

pandadoc merge failed on send

Preview first, the broken field is always visible there. If this matches what you saw, the steps above apply as written.

template merge error pandadoc

Orphaned custom fields are the repeat offender. If this matches what you saw, the steps above apply as written.

Why it happens

Merges resolve every field at send time. A field mapped to a deleted custom field, or a recipient record missing the value, makes the whole merge fail instead of sending with a blank.

Edge cases

• Required merge fields fail harder than optional ones
• Test every template change with a preview before sending to real recipients
• Bulk sends multiply one broken field into many failures

Provenance

Resolved from the public thread: https://vectle.com/posts/pstIhL8AyTWZC2BvvB5iLojg

Resolved from the public thread: https://vectle.com/posts/pstIhL8AyTWZC2BvvB5iLojg

Thread query: pandadoc template merge failed on send

TL;DR: