Event-driven archiving in ELO
Salesforce was connected to the ELO archive for centralised, automated document archiving. Rather than synchronising files periodically, Salesforce initiates archiving through Platform Events whenever relevant Office or PDF documents are available.
- months of project work
- 3months of project work
- integration pattern
- event-drivenintegration pattern
- through Custom Metadata
- configurablethrough Custom Metadata
What improved
A decoupled archiving integration that transfers relevant documents automatically and allows new object or file rules without modifying integration code.
- Client
- Anonymised - Industrial company
- Situation
- Business-relevant Office and PDF files needed to move reliably from Salesforce into a central ELO archive.
- Challenge
- Only relevant combinations of Salesforce object and file type should trigger the integration, and these rules needed to remain configurable without code changes.
- Objective
- Create a robust, asynchronous and flexibly configurable archiving flow between Salesforce and ELO.
- Role of nuvenio
- Integration design and technical implementation
- Approach
- Trigger events and metadata were defined, event publication implemented and the asynchronous flow tested end to end through MuleSoft into ELO.
- Implemented solution
- Salesforce publishes Platform Events for relevant objects and file types, which MuleSoft processes and transfers to ELO. Custom Metadata provides configurable control over the archiving rules.
- Technologies
- Salesforce Platform Events, MuleSoft, ELO, Custom Metadata, Office, PDF
- Project scope
- August to October 2025, design, development and end-to-end testing
Your contact
Discuss your project
We discuss your situation, put your questions in context and agree on a useful next step.
Free introductory call30–60 minutes · free, with no obligation
