Short answer
A Conga integration generates documents such as client agreements, account packets and reports from Salesforce data, and can route them for signature and approval.
How the Conga integration works
Conga Composer and related Conga products merge Salesforce data into Word, Excel, PowerPoint and PDF templates. Financial firms use it for onboarding packets, account forms and client reports. Templates are tied to the data model, so they need review when objects or fields change, including during a move to FSC on core.
What syncs
- Document templates populated from Salesforce records
- Generated files saved to the record
- Approval and signature routing
See the architecture diagram ↓
Integration options
- Conga Composer buttons and flows
- Conga Sign or DocuSign for signatures
- Batch generation for reports
What to plan for
- Template upkeep when fields change
- Licensing per user
- Performance with large related lists
Frequently asked questions
Do Conga templates break when we move to FSC on core?
They can, because object and field names change. Templates should be inventoried and updated as part of the migration.
Can Conga run from a flow?
Yes. Document generation can be triggered from Salesforce Flow.