Skip to content

Security

PGP Integration

Zynk's PGP integration adds file encryption and decryption to your automated workflows. Outgoing files are encrypted with the recipient's public key before they are uploaded or stored, and incoming files are decrypted with your private key before Zynk processes them. It suits businesses that exchange sensitive files with banks, 3PLs, suppliers and other trading partners over SFTP, FTP or cloud storage.

Available for

Capabilities may differ depending on the product.

Benefits

Why businesses connect PGP

Protected before it leaves

The Encrypt File step runs inside the workflow that creates the file, so an order export or remittance is protected before it is uploaded. Nobody has to remember to encrypt anything by hand before the transfer goes.

Incoming files opened for you

The Decrypt File step unlocks encrypted files collected from an SFTP server, cloud storage or a network folder, then hands the readable contents to the next step in the workflow without anyone opening them.

Meet partner security requirements

Some banks, logistics providers and trading partners will only accept PGP-encrypted files. Zynk meets that requirement within the automation that already moves the data, instead of relying on a separate desktop tool and a manual step.

One workflow from build to transfer

PGP sits alongside the FTP, SFTP, Amazon S3 and file connectors, so building, encrypting and uploading a file, or downloading and decrypting one, become steps in a single workflow rather than jobs on different machines.

Fewer people touching sensitive data

Because files move between steps automatically, staff no longer download, open and re-save sensitive files to pass them on. Fewer copies on desktops and shared drives means less personal and financial data left where it should not be.

Capabilities

What you can do with PGP

Every task the Zynk PGP connector can run, grouped by the direction data moves.

Actions in PGP

Tasks Zynk can automate in PGP

2 tasks

  • Decrypt file → in PGP
  • Encrypt file → in PGP

Need something that isn't listed?

Most PGP projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate PGP?

Encrypting one file by hand is easy. Doing it every day, for every partner, with the right key, is where things slip. Files go out unencrypted, keys live on one person's laptop, and incoming files sit in a folder until someone remembers to decrypt them so they can be processed.

Without integration

  • Files encrypted manually on one desktop before each upload
  • Encrypted partner files waiting in a folder until someone opens them
  • Transfers held up while the person with the key is on holiday
  • Readable copies of sensitive files left on shared drives

With Zynk

  • Files are encrypted inside the workflow that creates them
  • Incoming files are decrypted and passed straight to the next step
  • Scheduled workflows encrypt and decrypt whoever is in the office
  • Fewer manual copies, because files move between steps automatically

How it works

How the PGP integration works

  1. Step 1: Exchange keys

    Your trading partner shares their public key for the files you send them. You create a key pair and give them its public half, so they can encrypt the files they send to you.

  2. Step 2: Add the PGP steps

    Encrypt File goes after the step that builds an outgoing file, and Decrypt File after the step that downloads an incoming one. Each step uses the key that belongs to that partner.

  3. Step 3: Test with your partner

    Send the partner a test file and decrypt one of theirs, confirming that both sides can read the results before the workflow moves onto a schedule.

  4. Step 4: Run and monitor

    From then on the exchange runs unattended, with an alert if a file cannot be encrypted or decrypted, for example because a partner has replaced their key without telling you.

Example use cases for PGP integration

PGP and SFTP

Encrypt outgoing files before Zynk uploads them to a partner's SFTP server, and decrypt the files downloaded from it before they are imported anywhere.

From PGP to SFTP:Encrypted filesFrom SFTP to PGP:Downloaded files

View the SFTP integration →

PGP and FTP

Some partners still exchange files over FTP or FTPS. Encrypting the content first keeps the data protected on their server long after the transfer has finished.

From PGP to FTP:Encrypted filesFrom FTP to PGP:Downloaded files

View the FTP integration →

PGP and Amazon S3

Encrypt exports before they are written to an Amazon S3 bucket shared with a partner, and decrypt the files they leave there for you before processing.

From PGP to Amazon S3:Encrypted filesFrom Amazon S3 to PGP:Downloaded files

View the Amazon S3 integration →

PGP and File

Pick up encrypted files from a local or network folder, decrypt them for the next step, then move or archive the originals once processing has finished.

From PGP to File:Decrypted filesFrom File to PGP:Encrypted files

View the File integration →

Find your integration →

PGP integration FAQs

What does the PGP connector do in Zynk?
It provides two workflow steps, Encrypt File and Decrypt File. Encrypt File protects an outgoing file with your recipient's public key, and Decrypt File opens an incoming file with your private key. Both run inside Zynk workflows alongside transfer, conversion and import steps.
Can Zynk encrypt a file before uploading it to SFTP?
Yes. A typical workflow builds the file, encrypts it with the partner's public PGP key and uploads it to their SFTP server in a single run. SFTP protects the connection during transfer, while PGP protects the file itself once it has arrived.
Is PGP the same as SFTP?
No. SFTP encrypts the connection while a file is moving between servers. PGP encrypts the file itself, so it stays protected on the receiving server, in backups and wherever it is copied next. Many partners ask for both, and Zynk can apply them together.
Which keys do I need for PGP encryption?
To send encrypted files you need the recipient's public key. To receive them, you create a key pair, share the public key with your partner and keep the private key safe. Only the matching private key can decrypt a file encrypted for it.
Can Zynk decrypt files from my bank automatically?
Yes, where the bank delivers PGP-encrypted files to an SFTP server or folder that Zynk can reach. The workflow downloads each new file, decrypts it with your private key and passes the contents to whichever step comes next in your process.
Do I need a developer to add PGP to a workflow?
No. Encrypt File and Decrypt File are standard steps in Zynk Workflow, which is low-code. Our team can add them to an integration you already run or build a new file exchange with you, including the transfer and import steps around them.

See what Zynk can automate for your PGP setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a callSee pricing →