From Salesforce to Finished Documents and Back: The Complete Zapier Loop

Here is a complete round-trip: a record changes in Salesforce, Zapier carries the data into a DocupletionForms form, the data-merge selects and completes the right set of documents, and the DocupletionForms Salesforce API puts those finished documents back onto the original record. This post is the exhaustive version — every kind of Salesforce data you can send, and exactly what happens to it.

The value is in the breadth. Almost any event in Salesforce — a new lead, a closed opportunity, a single field flipping to a new value, a record on a custom object you built — can be the trigger. Once that data lands in the form, deterministic rules take over: the same inputs always select and populate the same documents, every time. Then they go home to Salesforce.

The exhaustive list: every Salesforce trigger that can feed the form

Salesforce’s Zapier app exposes a specific set of triggers. Each one is a different way to start the loop, and each carries the record’s data with it:

• New Record. Fires when a record of a chosen object — standard or custom — is created. The workhorse trigger; pick the object and every new one starts the loop.
• Updated Record. Fires when any record of a chosen object is updated. Good for re-generating documents when details change.
• Updated Field on Record. Fires when a specific field — a stage, a status, a type — changes on a chosen object, and outputs both the old and new values. This is the precision trigger: generate documents the moment Stage becomes “Closed Won” or Status becomes “Approved.”
• New Outbound Message. Fires from a Salesforce Flow or Workflow Rule whose criteria you define inside Salesforce, posting to a Zapier webhook. The most controlled and instant trigger, because the filtering logic lives in Salesforce itself.
• New Lead and New Contact. Dedicated triggers for the two most common intake points.
• New Task. Fires when a task is created — useful when a follow-up action should also generate paperwork.
• New Attachment to a Case, and New or Updated Attachment, Note, or Content Document on any object. Fires on document activity, so an uploaded file can itself kick off a generated response set.

Because New Record, Updated Record, and Updated Field on Record all let you choose the object, they are not one trigger each — they are one trigger multiplied by every object in your org.

Every object, standard and custom

This is where “how many ways” becomes real. The object-based triggers work on any Salesforce object, so the list of data types you can send is essentially the list of things you track. Standard objects include:

• Lead, Contact, Account, and Person Account
• Opportunity and Opportunity Line Item
• Case and Solution
• Campaign and Campaign Member
• Quote, Contract, Order, and Asset
• Product and Price Book Entry
• Task and Event

And then every custom object you have built — a Matter, a Policy, a Loan, a Project, a Claim, a Deal — is equally available as a trigger. A custom object is often the best source, because it already models exactly the thing your documents are about.

Whatever object you pick, the trigger carries its fields: names and addresses, amounts and dates, picklist values, record type, owner, and the related record IDs. Those field values are the raw material the data-merge runs on.

How the data enters DocupletionForms

Once Zapier holds the Salesforce data, it hands it to DocupletionForms as a form submission: Webhooks by Zapier can post the mapped fields into a DocupletionForms form, or the DocupletionForms step in Zapier can create the submission directly. Either way, the Salesforce fields land in the form’s fields — the same intake the form would receive from a person, now populated from the CRM. From the engine’s point of view, a submission is a submission; the source does not change how deterministically it is processed.

What the data-merge does with it

This is the point of the whole loop. The submitted field values drive conditional logic that selects which documents are needed and completes them — not one document, but the full set the situation calls for. A Salesforce Opportunity with a particular type, stage, and amount deterministically produces a specific contract, cover letter, and schedule; a custom Matter record produces its whole packet. Because the rules are fixed, the same record always yields the same documents. Change the record, and only the parts that depend on what changed change in the output. That predictability is the reason to put a CRM behind a rule-based engine rather than a generative one.

Returning the documents to Salesforce

The loop closes with the DocupletionForms Salesforce API integration, which pushes the finished documents back onto the originating record — so the contract, packet, or disclosure set lands as files on the very Opportunity, Case, or custom-object record that started it. The person in Salesforce never leaves Salesforce: they change a record, and the completed documents appear on it. Record data and the generated files travel as distinct steps, which keeps the file handling explicit and controllable.

Worked examples

Opportunity closed: Updated Field on Record (Stage becomes Closed Won) → Zapier → form → contract, order form, and welcome letter generated → files posted back to the Opportunity.

New case: New Record on Case → the response and disclosure set for that case type is completed → returned to the Case.

Custom Matter: New Record on a custom Matter object → the full matter packet is selected by practice area and jurisdiction → attached to the Matter.

New lead: New Lead → an intake agreement and onboarding set is generated → stored on the converted Contact or Account.

Requirements and limits

• API-enabled Salesforce edition. Zapier connects to Salesforce through its API; Enterprise, Unlimited, Performance, and Developer editions include it, and Professional needs the API add-on.
• Admin approval of the connected app. A Salesforce admin must allow the Zapier connected app; orgs also have a connected-app access limit to keep in mind.
• Data versus file. Moving the record’s field data and posting the generated PDF back are separate operations; confirm both when you scope the build.

A sensible first build

The connective tissue, briefly

Three pieces do the plumbing. Salesforce triggers decide when and on what the loop starts. Zapier carries the field data into the form with no code. And the DocupletionForms Salesforce API carries the finished documents home. In the middle sits the deterministic engine that turns a record’s fields into the correct, complete set of documents — the same way, every time.

If your team lives in Salesforce and drowns in document assembly, this is the round-trip worth building once. Start with DocupletionForms and wire your CRM to it.