8 document engines. API access. Stop writing Apex for document generation.
REST API and Apex invocable actions. 8 pre-built engines for 6 output formats. Custom metadata types for full configurability. Full sandbox support. Build on NimeDocs -- don't rebuild it.
Before and after NimeDocs
Stop maintaining custom document generation code. Delegate it to a managed package with 8 engines and a REST API.
8 engines, one API call
Pass a template ID and record ID. Get back a generated document in any of 6 formats.
Top features for Developers
APIs, engines, metadata types, and extensibility points designed for developers who build on the Salesforce platform.
DocxDocEngine, PptxDocEngine, XlsxDocEngine, HtmlDocEngine, CsvDocEngine, NimeSheetDocEngine, PptxMergeEngine, and PresentPptxEngine. Each engine is purpose-built for its output format with full merge-field resolution, formula evaluation (80+ functions), and Salesforce data binding via WIRE(), QUERY(), and RECORD().
Trigger document generation from REST endpoints, Apex triggers, Flow, or Process Builder. JSON request with template ID and record context, JSON response with document ID. Invocable actions work natively in Flow Builder for admin-friendly integrations. No callout limits -- 100% on-platform.
Template__mdt stores template definitions and configuration. Apps__mdt defines application-level settings. Global_Config__mdt controls org-wide behavior. All deployable via change sets, metadata API, and SFDX -- standard Salesforce DevOps workflows.
Build multi-step document workflows programmatically with 10 step types: GenerateDoc, Email, UpdateRecord, CreateRecord, HttpCallout, Wait, Condition, AttachFile, Chatter, and Flow. Chain steps with conditional branching. Monitor execution with per-step status, progress percentage, and elapsed time via the API.
Install in sandbox with full feature parity. Test templates, processes, and API integrations before production. Deploy configurations via change sets, metadata API, or SFDX. Custom metadata types (Template__mdt, Apps__mdt, Global_Config__mdt) travel with your deployment pipeline.
8 engines. 6 formats. Zero custom code.
Each engine is purpose-built for its output format with full template merge, formula evaluation, and Salesforce data binding.
OOXML-compliant Word generation with tables, images, headers/footers, conditional sections, and full merge-field support. Output to DOCX or PDF.
Three presentation engines: template merge, slide assembly from multiple sources, and Fabric.js canvas-based generation with 14 chart types and 20+ themes.
Two spreadsheet engines: standard template merge and NimeSheet with 80+ formula functions, freeze panes, cell validation, comments, multi-sheet support, and WIRE() data binding.
HTML output with full merge-field resolution. Use for email bodies, web-ready documents, or as an intermediate step for PDF conversion.
CSV generation for data exports, integrations, and bulk operations. Merge Salesforce data into structured CSV output with WIRE() and QUERY() data binding.
Get started in 4 steps
From sandbox install to production deployment with standard Salesforce DevOps.
Install the managed package in your sandbox. Full feature parity with production. Assign permission sets and configure Global_Config__mdt for org-wide settings.
Review REST endpoints for document generation, template management, and process execution. Test Apex invocable actions in Flow Builder. Inspect custom metadata types for configuration options.
Trigger document generation from an Apex trigger, Flow, or external system via REST. Pass template ID and record context. Get back a ContentVersion document ID. Chain with process steps for multi-step workflows.
Install the managed package in production. Deploy Template__mdt, Apps__mdt, and Global_Config__mdt via change sets or SFDX. Templates and process configurations migrate with your standard deployment pipeline.
Ready to stop writing document generation code?
8 engines. REST API. Apex invocable. Custom metadata. Full sandbox support. Ship document features in hours, not sprints.