A Decrypt With GPG node decrypts each incoming file with a private key from your GPG Key Manager and passes on the decrypted file. Use it to decrypt the files a partner encrypted for you before the nodes after it convert, read, or route them.

Decrypt With GPG accepts only file items, because it reads a file's contents. GPG decryption applies to files up to 5 GB.

Settings

The node takes the key to decrypt with, selected from the GPG Key Manager. Decryption uses your private key, so the key entry must be a key pair. The optional destination path takes the same tokens and templates as every destination. With no destination, the decrypted file is written in the original's folder, named by removing .gpg or .pgp from the original's name, or by adding .decrypted when the name has neither. The overwrite setting is off by default, so an existing file at the destination fails the item with processing-failure/destination-exists instead of being replaced.

What the Next Node Receives

Decrypt With GPG passes on one file item for each decrypted file. The encrypted original is unchanged.

Errors

A file that was not encrypted for the selected key fails that item, and a file that no longer exists when the node runs fails with a not-found error. Error Handling rules on the node determine what happens to a failed item.

Decrypt With GPG vs. GPG Decryption on a Folder

GPG Decryption as a Folder Setting decrypts every file when it is uploaded or copied into that folder, and it can try any private key in the GPG Key Manager or only the keys you select for that folder. The Decrypt With GPG node decrypts where you place it in the graph, with the key you select, and only the files routed to it. Use the Folder Setting when every file a partner uploads to a folder must be stored decrypted. Use the node when decryption is one node in a workflow, for example decrypt, then convert, then route by contents.