Resources · Make integration

Encryptor Make integrationAutomate Encryptor with Make.

Encrypted data can be opened and signed without leaving your scenario. The Encryptor Make integration gives you 4 action modules: three to decrypt AES or PGP content and one to create a digital signature. This guide shows which one to pick and how to wire your first scenario.

Try the Encryptor integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Encryptor Make integration do?

The Encryptor Make integration is a built-in Make app that turns encrypted content back into readable data and stamps content with a digital signature, right inside a scenario (the automation you build in Make, a chain of modules). Each module is one brick of that chain, and Encryptor adds four of them.

Read a PGP message sent by a partner. A supplier sends orders protected with PGP, an asymmetric method built on a private key, a public key and a session key. Place Decrypt a PGP message right after the module that receives the text, and the next modules get the plain content they can route or store.

Open AES content shared by an internal tool. AES is symmetric: the key that locked the data also unlocks it. When a system of yours stores values encrypted this way, AES Decrypt (simple) or AES Decrypt (advanced) gives the readable value back to the scenario.

Prove a document was not altered. Create digital signature produces a unique hash with SHA-1 or SHA-256, which a recipient can compare with their own result.

Know the boundaries before you start. Encryptor has no trigger, so the scenario starts from another app or from a schedule. None of its four modules encrypts data, they only decrypt or sign, and it has no Make an API Call module. If you also work with n8n, the n8n vs Make comparison helps you place both tools, and the Make review covers the editor itself. To learn scenario design properly, see the Make training.

Connect

How do you set up Encryptor in Make?

  1. 01

    Add an Encryptor module

    Open your scenario, click the + where the module should go, search for Encryptor and pick the module you need. It sits among the built-in apps of Make, next to the other tools of the editor.

  2. 02

    Skip the connection step

    Most apps ask you to click Create a connection to link your account (a connection is your account of the app linked to Make once). Encryptor does not need one, so there is nothing to authorize and no password to paste.

  3. 03

    Fill the module fields

    Map the encrypted text or the content to sign from the previous module, then enter the key your data was protected with. Keep that key where your team already stores its secrets, not in a note on the scenario.

First scenario

Your first scenario with Encryptor

GoalWhen an encrypted message comes in from another app, Make decrypts it with PGP and signs the readable result.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the app that receives the encrypted message, such as your mailbox or your form tool.

  2. 02

    Add Decrypt a PGP message

    Click the + on the right of that first module, search Encryptor and choose Decrypt a PGP message. No connection is needed, so you go straight to the fields.

  3. 03

    Map the message and the key

    Map the encrypted text coming from the first module into the Encryptor fields, then provide the private key that matches the public key your sender used.

  4. 04

    Add Create digital signature

    Add Create digital signature after the decryption and map the readable content into it. Pick SHA-1 or SHA-256 for the hash, depending on what your recipient checks.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble on each module to read the bundles it received: the decrypted text first, then the signature.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each Encryptor module that processes a bundle counts as one operation on your plan.

Modules

What can the Encryptor modules do?

Encryptor gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Encryptor1

AES Decrypt (advanced)

ActionIn the docs only

This module hands your scenario the readable version of AES encrypted data, and, as its name suggests, likely more settings to adjust than its simple sibling. AES uses one shared key to lock and unlock the data.

When to use it
the simple module does not match how your data was encrypted, and you need to set more options yourself.
Watch out
open both AES modules in the editor and compare their fields before choosing, since the doc does not describe the difference.
Encryptor2

AES Decrypt (simple)

ActionIn the docs only

Here you get the plain value back from AES encrypted content with the fewest settings to fill, which makes it the natural first try for anyone new to encryption in Make.

When to use it
a system you control encrypted a value with a key you already hold, and you just need the text back to route it.
Watch out
AES is symmetric, so the key must be exactly the one used to encrypt.
Encryptor3

Create digital signature

ActionIn the docs only

You get a unique hash of your content, computed with SHA-1 or SHA-256, that proves later whether that content changed along the way.

When to use it
a contract, an export or a message leaves your scenario and the recipient wants to check it arrived untouched.
Watch out
the recipient has to compute the hash with the same algorithm, or the two values will never match.
Encryptor4

Decrypt a PGP message

ActionIn the docs only

A PGP protected message becomes readable text that the next modules can parse, store or forward. PGP pairs a public key, used by the sender, with your private key, used here.

When to use it
a partner or a supplier sends you content encrypted with the public key you shared with them.
Watch out
only the private key matching that public key can open the message, so keep them paired.
Need help

Need help automating Encryptor with Make?

A person reads every message.

FAQ

Encryptor and Make: frequent questions

01Is the Encryptor Make integration free?
Yes. Encryptor is a standard built-in app, available from the Make Free plan onward. The Free plan does come with limits that apply to every scenario: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run on a bundle counts as one operation, so a scenario chaining two Encryptor modules uses two operations per message.
02What is needed to use Encryptor in Make?
Only a Make account and the keys your data depends on. The Make documentation says Encryptor does not need any connection, so there is no account to create and no authorization window to approve. What you do need is the right key material: the shared AES key for the two AES modules, and the private key matching the sender's public key for the PGP module. The signature module needs only the content to hash and the hash algorithm you pick in its fields.
03Can an Encryptor scenario start on its own?
Not from Encryptor itself, because the app has no trigger module. A scenario always starts on its first module, so put another app there: the one that receives the encrypted message or file. The scenario then runs on the schedule set on that first module, every 15 minutes by default, or as soon as that app calls Make if its trigger is instant. Encryptor modules then act on each bundle that flows through, one item at a time.
04What if an Encryptor module is missing?
Check the other built-in apps of Make first. Encryptor has four modules, three for decryption and one for signatures, and no Make an API Call module to reach anything else. If your need is encrypting data or another algorithm, look for a different app in the Make catalog that covers it. When nothing fits, the Hack'celeration team can look at the flow with you and suggest another way to build it in your scenario.
05Make or n8n for encryption tasks?
It depends on where the rest of your automations already live. Encryptor is a Make built-in app with four modules and no connection to set up, which keeps it easy to drop into an existing Make scenario. Many apps also have an equivalent node in n8n, so check what that tool offers for your algorithm before moving anything. The deciding criteria are the modules you need, the team that will maintain the scenario and the tools already connected on each side.
Same platform

Other docs you might need on this stack.

Browse all integrations