PGP Encryption
Infoveave Data Automation — File Preparation
Sensitive file in. PGP-encrypted archive out. Only the key holder can open it.
Automated pipelines that deliver sensitive data to external partners — payroll, patient records, financial transactions — must encrypt files in transit. PGP encryption provides asymmetric security: the workflow encrypts with the recipient's public key, and only the corresponding private key can decrypt it. No shared password to manage or leak. PGP Encryption adds this step directly into the pipeline, so every external delivery is encrypted without manual intervention.
What PGP Encryption does
Encrypt files using PGP public key cryptography inside your Infoveave workflow before external delivery. Protect sensitive data exports, financial files, and healthcare records without any manual encryption step.
When to use PGP Encryption
- You need to deliver sensitive files (payroll, patient records, financial data) to an external partner that uses PGP decryption
- Your compliance requirements (HIPAA, GDPR, PCI DSS) mandate that data in transit is encrypted
- You want to replace shared-password ZIP encryption with stronger asymmetric public-key encryption
- Your workflow pipeline generates output files that must be encrypted before email attachment or SFTP upload
When to avoid it
- Your partner cannot receive or decrypt PGP-encrypted files — coordinate with them first on the encryption method
- You only need password protection rather than asymmetric key encryption — use Zip Files with a password instead
Where it fits in your Infoveave automation
PGP Encryption is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use PGP Encryption
Real scenarios where this transformation saves hours of manual work.
HIPAA-Compliant Patient Data Export
Patient records extracted for a third-party research partner are encrypted with the partner's PGP public key before being uploaded to the shared SFTP location. Only the research partner's private key holder can decrypt and access the records.
Payroll File Encryption
The monthly payroll export is encrypted with the payroll bureau's public key immediately after generation. The encrypted .pgp file is attached to the automated email notification, ensuring no unencrypted salary data is ever transmitted.
Supplier Pricing Data Protection
Confidential pricing agreements sent to distribution partners require encryption. PGP Encryption protects each partner's file individually using their respective public keys before SFTP delivery.
See PGP Encryption in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
/keys/partner_public.ascInput Data
| File |
|---|
| payroll_april_2026.csv |
Output Data
| File | Format | Note |
|---|---|---|
| payroll_april_2026.csv.pgp | .pgp encrypted | Decryptable only with matching private key |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Public Key File Path
The full path to the recipient's PGP public key file (.asc or .gpg format). The workflow server must have access to this file. The file can be placed in a shared directory or referenced via an environment variable. Public keys are safe to store in workflow configuration — they cannot be used to decrypt data.
Frequently asked questions
Everything you need to know about PGP Encryption in Infoveave.
Also in File Preparation — and what runs before & after
Transformations in the same family as PGP Encryption, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
PGP Encryption is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
