Infoveave Data Automation — File Preparation
Encrypted partner file in. Decrypted, processable data out. Fully automated.
Organizations that receive encrypted data deliveries from partners, government agencies, or banks face a manual decryption step before any processing can begin — breaking the automation chain. PGP Decryption removes that friction by integrating decryption directly into the ingestion workflow. The pipeline receives the .pgp file, decrypts it using the stored private key, and immediately passes the plaintext to the next processing step — zero manual intervention.
Automatically decrypt PGP-encrypted files received from partners, government agencies, or secure data providers inside your Infoveave workflow. Use your private key to unlock encrypted archives without any manual decryption step.
PGP Decryption 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.
Real scenarios where this transformation saves hours of manual work.
A bank delivers daily transaction files encrypted with the organization's PGP public key via SFTP. PGP Decryption automatically unlocks the file each morning, passing the CSV to the reconciliation pipeline without requiring a finance team member to manually decrypt it.
An insurance partner sends encrypted claims data weekly. PGP Decryption uses the organization's private key to unlock the file, making the claims data immediately available for the validation and database loading pipeline.
A government agency provides encrypted compliance datasets. PGP Decryption integrates into the ingestion pipeline so that as soon as the encrypted file arrives, it is decrypted and processed — satisfying both the security requirement and the SLA for data processing.
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
.csv/keys/my_private_key.asckeyPassphraseInput Data
| Encrypted File |
|---|
| transactions_2026-04.csv.pgp |
Output Data
| Decrypted File | Format | Status |
|---|---|---|
| transactions_2026-04.csv | CSV | Decrypted, ready for ingestion |
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Extension
The file extension for the decrypted output file. Tells the workflow what format the plaintext file should be treated as after decryption. Example: .csv, .xlsx, .txt.
Private Key File
Path to your PGP private key file (.asc or .gpg). The workflow server must have read access to this file. Never embed the private key directly in the workflow configuration — reference it by file path and restrict access to the file via OS-level permissions.
Password
The passphrase protecting your PGP private key. Store this in a workflow secret or environment variable rather than as plain text in the activity configuration.
Everything you need to know about PGP Decryption in Infoveave.
Transformations in the same family as PGP Decryption, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
PGP Decryption 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?