Salesforce Excel Add-In: How to Connect, Export, and Generate Excel Reports Without Code 

Word isn’t the only format a business runs on. Finance wants a formatted Excel report with real calculations built in, not just a data dump. Sales ops wants a pipeline summary that already has the pivot table structure set up, ready to hand off rather than rebuilt from scratch every week. The 360 InstantDocs Excel add-in exists for exactly that gap, working the same way the Word Add-In does, but built for teams whose output needs to be a working spreadsheet rather than a document. 

This guide covers what the Excel add-in actually does, how to connect Salesforce data to an Excel template, how generation works once that template is built, and where Excel output makes more sense than Word or PDF for a given use case. 

No more reformatting a PDF back into a spreadsheet by hand. 

Book a demo

What Is the 360 InstantDocs Excel Add-In? 

The Excel add-in works the same way the Microsoft Word Add-In does, just inside Excel instead. It installs directly into Excel, giving you a sidebar where Salesforce fields can be inserted into a spreadsheet as merge fields, the same drag-or-insert pattern that already works for Word templates. 

The difference is what comes out the other end. A Word template produces a formatted document, a contract, an offer letter, something meant to be read top to bottom. An Excel template produces a working spreadsheet, rows of data, formulas, and structure that’s meant to be calculated on, sorted, or built into a pivot table, not just read. Both connect to the same live Salesforce data underneath, standard or custom objects, relationship fields, the works, the only real difference is the shape of what gets generated at the end. 

Building an Excel Template with Salesforce Merge Fields 

Template creation follows a familiar pattern if you’ve already built a Word template in 360 InstantDocs. Open Excel, activate the add-in, and the sidebar surfaces available Salesforce fields the same way it does in Word, insert a field at your cursor, and it drops into the selected cell as a merge placeholder tied to live Salesforce data. 

Structure it like any Excel report you’d build manually, header rows, column labels, and formulas that reference the cells where merge data will land. A pipeline summary template, for instance, might merge in Opportunity Name, Amount, Stage, and Close Date across a set of rows, with a SUM formula at the bottom totaling the Amount column automatically once real data populates it. Relationship fields work here too, the same dot notation used in Word templates lets you pull in Account.Name or Contact.Email alongside the primary object’s own fields, so a template isn’t limited to data sitting directly on the record it’s generating from. 

Generating Excel Reports from Salesforce Records 

Once a template exists, generation works through the same flow as Word or PDF output, triggered from a record, a list view, or a Salesforce Flow, whichever fits the use case. Choose Excel as the output format at generation time, and the template’s merge fields populate with live data from the selected record or records, producing a finished spreadsheet rather than a document. 

This is particularly useful for reports that need to go somewhere beyond a quick read, a finance team that wants to open the generated file and immediately start filtering, sorting, or building a pivot table on top of it, rather than reformatting a PDF’s worth of numbers back into a spreadsheet by hand first. The generated file saves to the Salesforce record the same way a Word or PDF document would, so it’s not a separate, disconnected export sitting in someone’s downloads folder, it stays attached to the record it came from. 

Weekly exports, monthly summaries, all on autopilot. Let’s map your cadence. 

Schedule a call

Bulk Generation for Excel Reports 

Bulk generation works on Excel templates the same way it does for Word and PDF, select the object in the Bulk Generation wizard, choose a list view or report containing the records you want, pick the Excel template, and generate for all selected records in one action. 

This fits recurring reporting needs particularly well, a weekly pipeline export built from a consistent template, a monthly account summary generated across every active client at once. Rather than manually pulling a report and reformatting it into a spreadsheet every cycle, the same template runs against whatever records are currently eligible, producing a consistently formatted Excel file without anyone rebuilding structure or re-entering formulas each time. 

Common Use Cases for the Excel Add-In 

Sales operations teams use Excel templates for pipeline reports that need real calculation built in, weighted forecast totals, stage-by-stage breakdowns, structured for further analysis rather than just a read-only summary. Finance teams lean on it for reconciliation-style reports, structured Excel output that can be cross-referenced against numbers from other systems without needing to manually rebuild a spreadsheet from a PDF or CSV first. 

Account management teams often use it for structured account summaries, an Excel file per client with consistent formatting and calculated fields, generated the moment it’s needed rather than assembled by hand. And operations teams generally reach for it whenever the deliverable is meant to be worked on further, not just read, since that’s the core distinction between reaching for a Word or PDF template and reaching for an Excel one. 

Excel vs Word vs PDF: Choosing the Right Output 

The choice usually comes down to what happens to the document after it’s generated. If it’s meant to be signed, sent to a customer as a finished document, or read top to bottom as prose, Word or PDF is the right call, a contract, an offer letter, an invoice with branding and layout. If it’s meant to be calculated on, filtered, sorted, or built into a pivot table, Excel is the better fit, a pipeline report, a reconciliation sheet, any output where the value is in what someone does with the numbers after opening it, not just in reading them. 

Plenty of teams end up using both from the same Salesforce data, a Word contract for the customer-facing side of a deal, an Excel report built from the same Opportunity records for internal pipeline analysis. Since both template types connect to the same underlying data and generation workflow, switching between them is a matter of choosing the right template for the job, not learning a separate tool.