How to Generate Documents in Salesforce: Step-by-Step Guide (2026)

The first thing to understand about how to generate documents in Salesforce is that it requires a dedicated AppExchange app. You also need administrator permissions to create templates and buttons, and at least one Salesforce object with populated records to generate from. Salesforce does not include document generation as a core platform feature.

When choosing a tool, the most important architectural question is whether it is native or integration-based. Native tools run entirely inside Salesforce using Apex and Lightning. Integration-based tools connect via API from an external server, which means your Salesforce data leaves the platform on every generation event.

How to generate documents in Salesforce involves six steps: building a template with merge fields, connecting it to a Salesforce object, adding a generation trigger, testing the output, generating the first live document, and optionally configuring e-signature. Most teams have their first document generating within a few hours of setup.

The document template defines the layout, content, and structure of every document your tool will generate. You build it once, insert merge fields where Salesforce data should appear, and the tool uses it every time that document type is requested.

The template is the foundation of how to generate documents in Salesforce. Start with the structure of the document: for a contract, that means sections for parties, terms, payment schedule, and signatures. For an invoice, it means a header, line item table, totals, and payment instructions.

Next, insert merge fields. A merge field is a placeholder that tells the generation tool where to pull data from Salesforce. The syntax varies by tool, but the logic is consistent: you reference the object name and the field's API name.

The field name you use must be the API name of the field, not the label. To find a field's API name, go to Setup, open Object Manager, select the relevant object, and click Fields and Relationships. Custom fields always end in __c.

For documents with line items — invoices, quotes, purchase orders — use a repeat block to generate one row per related record. The result is a dynamically-sized table that grows or shrinks based on the number of line items on the record.

Connecting the template to a Salesforce object tells the generation tool which record to use as the data source when a user triggers generation. A contract template connects to the Opportunity or Contract object. An invoice template connects to the Opportunity or a custom billing object. An offer letter connects to the Contact or a custom candidate object.

At this stage you also configure three things that affect every document generated from this template:

For users to generate documents, they need a trigger — either a button on the record page layout or a Salesforce Flow that fires automatically based on a record event. Buttons are the most common starting point. Flows are the path to full automation.

To add a custom button in Salesforce, go to Setup and open the Object Manager for the relevant object. Select Buttons, Links, and Actions, and create a new button. Configure it to call the document generation tool's action or Lightning component, then add it to the relevant page layout or Lightning record page.

For automated generation without any user click, use a Salesforce Flow. A record-triggered Flow can fire when an Opportunity moves to Closed Won, when a contract record is created, or when a specific field changes. The Flow calls the document generation action as one of its steps.

Before rolling the template out to your team, generate a test document from a real record and verify every merge field, every conditional block, and every line item table resolves correctly. A template that works perfectly on one complete record may produce unexpected output on a record with missing data, a different record type, or a different currency.

Run at minimum these four test cases:

With the template built and tested, knowing how to generate documents in Salesforce from any record takes seconds. Open the record, click the generation button, confirm any settings if prompted, and the document generates and attaches automatically.

The exact sequence is:

For most documents, the final step in how to generate documents in Salesforce end-to-end is configuring e-signature. If your document generation tool includes native e-signature, you can configure the signing workflow as part of the generation step so a user can generate and send for signature in a single action.

Set up the following in the template or tool configuration:

With a native tool, the signing experience is handled inside Salesforce's trust boundary. Signing events — who viewed the document, when, from which IP address, using which authentication method — are recorded as Salesforce records in your org. The completed document and its Certificate of Completion are stored as Salesforce Files on the linked record.

Tools that use a third-party signing service store those audit records externally. For teams in HIPAA, SOX, or GDPR environments, that distinction matters. See our post on Salesforce document compliance audit trails for the full picture.

To generate documents in bulk from a Salesforce list view, select the records you want to process, click the bulk generation button, choose a template, and the tool generates a separate document for each selected record simultaneously. Each document is populated from its own record's data and attached to that record automatically.

The same template used for single-record generation works for batch runs. There is no separate batch template — the difference is only in how the trigger fires. Instead of clicking a button on one record, you select multiple records in the list view and trigger generation for all of them at once.

For teams generating hundreds of documents per month — renewal campaigns, invoice runs, HR cohort onboarding, compliance certifications — batch generation is the feature that makes the tool genuinely valuable at scale. For a detailed look at how this works and what it saves, see our guide on bulk document generation in Salesforce.

When learning how to generate documents in Salesforce, the most common problems are blank merge fields, missing related record data, documents not attaching to the record, and formatting that breaks in the output. All four have straightforward fixes.