Extension Libraries
Integration Soup Extension Libraries add extra workflow features that you can install alongside Integration Soup and Integration Host.
These extensions are distributed as MSI installers and are documented here as product features you can add to your workflows.
Available extension libraries
- HTML to PDF
- RTF to PDF
- Azure Activities
- AWS Activities
- Encryption Activities
- SFTP Activities
- ZIP Activities
- Validate HL7 Transformer
- HL7 Value Transformers
Download installers
All extension library installers are published here:
Direct MSI links:
- IntegrationSoup.HtmlToPdfActivities.msi
- IntegrationSoup.RtfToPdfActivities.msi
- IntegrationSoup.AzureActivities.msi
- IntegrationSoup.AwsActivities.msi
- IntegrationSoup.EncryptionActivities.msi
- IntegrationSoup.SftpActivities.msi
- IntegrationSoup.ZipActivities.msi
- IntegrationSoup.ValidateHl7Transformer.msi
- IntegrationSoup.HL7ValueTransformers.msi
.NET Framework prerequisite
The bridge-enabled Extension Library installers require Microsoft .NET Framework 4.8 or later on each computer where their MSI is installed. This applies to all ten packages, including HL7 Value Transformers and Validate HL7 Transformer, because installation uses a shared helper built for .NET Framework 4.8. .NET Framework 4.8.1 also satisfies this requirement; .NET Framework 4.7.2 does not.
The installer checks the framework before a new installation or upgrade. If it is missing or too old, setup stops with a message directing the user to the .NET Framework 4.8 Runtime download. Install the runtime, restart Windows if requested, and run the Extension Library installer again. Maintenance and uninstall remain available if the runtime is removed after installation.
To check a computer, run this single line in PowerShell:
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full').Release
A release value of 528040 or higher meets the requirement. The value 461814 identifies .NET Framework 4.7.2 and requires an update. See Microsoft's framework detection guidance.
The HL7 validation runner additionally requires the Microsoft .NET 10 Runtime (x64). Its installer reports a missing runtime before a new installation or upgrade.
Installation errors
Interactive installers display errors and an Installation failed screen with the diagnostic log location. Verbose MSI logging is automatic: logs normally appear as MSI*.log in the installing account's temporary folder. Send the log to support if setup fails. Quiet deployments return an error code and write a log without showing dialogs. If Windows cannot open the MSI file, package-defined logging cannot start.
General installation flow
- Run the MSI on the Integration Soup server.
- Restart the Integration Soup service if it is not restarted automatically.
- Open the Workflow Designer and add the new activity to your workflow.
- Configure the activity parameters and message template as described on the extension page for that feature.
Notes
- Some extensions have extra server prerequisites, such as a browser for HTML to PDF or LibreOffice for RTF to PDF.
- ZIP Activities uses a persistent out-of-process runner and the .NET ZIP implementation included with the installer; no separate ZIP application is required.
- In version 4, HL7 Value Transformers runs as transformer code loaded from
Custom Libraries. - Version 5 deployment uses registered isolated runners and requires bridge-enabled Extension Library installers.
- Each extension page below explains the exact parameters to set, what to place into the activity message, and what the response message contains.