Resources · Make integration

HEU Make integrationAutomate HEU with Make.

Can Make create and follow up HEU documents for you? The HEU Make integration gives you 10 modules: one scheduled trigger, five actions and four searches. This guide shows how to connect your account and build a first scenario step by step.

Try the HEU integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HEU Make integration do?

The HEU Make integration links your HEU account to Make so a scenario (the automation you build, a chain of modules) can create documents, look up PDF documents and their signers, and nudge people who still have to sign. Each module is one brick of that chain, and you place them without writing code.

Paperwork that starts on its own. Put Create a PDF document or Create a document after a trigger from another app, such as a form or a CRM, and the file appears in HEU without anyone opening it.

Signers who get chased for you. List PDF document signers returns who is attached to a document, and Send a signature reminder for a PDF document sends the nudge. Sales and HR teams stop writing those follow-up messages by hand.

A clean picture of what exists. Watch documents and List PDF documents feed your HEU documents into the rest of your stack, for a report or an archive in another tool.

A word of caution: Make's own help page for HEU is flagged as limited documentation, so it gives no field list and no description per module. Test each module with Run once before you rely on it. If you are new to the editor, the Make training walks through the basics, Make troubleshooting covers common errors, and n8n vs Make helps if you are still choosing a platform.

Connect

How do you connect HEU to Make?

  1. 01

    Add an HEU module

    In your scenario, click the +, search for HEU and pick any module. Then click Create a connection. A connection is your HEU account linked to Make once, and every HEU module reuses it afterwards.

  2. 02

    Name it and authorize

    Give the connection a clear name if you like, which helps when you run several accounts. Then either approve Make on the HEU page that opens, or paste the key HEU gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now read your HEU data. If the module fields fill with choices you recognize, the link works and you can move on to the scenario.

First scenario

Your first scenario with HEU and Make

GoalWhen a new record lands in another app, Make creates a matching PDF document in HEU.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app that holds your source data, a form tool or a spreadsheet, and its trigger module.

  2. 02

    Connect the source app

    Click Create a connection for that app and fill its fields. Make lists the forms, sheets or objects it can read, so you choose from a menu.

  3. 03

    Add Create a PDF document

    Click the + on the right of the first module, search HEU and pick Create a PDF document. Link your HEU account the way the connection section explains.

  4. 04

    Map the data

    Fill the HEU fields by clicking into them and picking values from the first module, such as a name or an email. Each record that arrives is one bundle, one item passed along.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open HEU and check that the document looks the way you expect.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts an HEU scenario

1 module starts a scenario when something happens in HEU. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HEU as soon as it happens.

HEU1Watch documents

Watch documents

triggerIn the docs only

Watch documents hands your HEU documents to the next modules, so a scenario can react to them without you exporting anything. Make gives no official description for it, and its type is read from its name, so confirm what it returns with a first test.

How it fires
scheduled, Make checks the app on the scenario's schedule. It is a scheduled trigger (the clock badge), not an instant one, so documents are picked up at the next check.
When to use it
when an HEU document should be copied to a shared drive or logged in a tracking sheet.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes.
Modules

What HEU can do in Make

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

HEU1

Create a PDF document

ActionIn the docs only

You get a new PDF document in HEU built from data that came from another app, with nobody copying details by hand. It is the natural first action when a signed deal or a completed form should turn into paperwork.

When to use it
after a CRM or form trigger, when the output must be a PDF.
Watch out
the documentation lists no fields, so check each one after a Run once.
HEU2

Create a document

ActionIn the docs only

This one also adds a document to HEU, but its name does not say PDF, which sets it apart from the module above. Pick it when the PDF version is not what you need.

When to use it
when you want a document record in HEU fed by another tool, for example a new client file.
Watch out
Make publishes no description telling the two creation modules apart, so compare their results with a test before choosing.
HEU3

Get a PDF document

ActionIn the docs only

Fetches one PDF document you already know, so the modules that follow can use its details. Where the list modules return many items, this one targets a single document.

When to use it
right after Watch documents or a search, when you need the full record of one document to pass it on.
Watch out
the documentation does not say how the document is picked, so map it from an earlier module and check the result with Run once.
HEU4

List PDF document placeholders

SearchIn the docs only

Going by its name, it shows the placeholders of a PDF document, so you can see what a document holds before feeding it data. As a search, it can return zero, one or several bundles.

When to use it
while building a scenario, to check which slots a document offers.
Watch out
each placeholder returned is a separate bundle, and later modules run once per bundle.
HEU5

List PDF document signer placeholders

SearchIn the docs only

Going by its name, it returns the placeholders tied to signers on a PDF document, likely the spots where each person is meant to sign. It differs from the general placeholder list by keeping only the signer side.

When to use it
before sending a document out, to confirm every signature spot has someone behind it.
Watch out
an empty result is possible, so handle the case where nothing comes back.
HEU6

List PDF document signers

SearchIn the docs only

Lists the people attached as signers to a PDF document, so your scenario knows who is involved. Pair it with the reminder module to follow up only with the right people.

When to use it
when a manager wants the list of people on a contract pushed to a sheet or a chat channel.
Watch out
several signers means several bundles, and each one costs an operation in the modules that follow.
HEU7

List PDF documents

SearchIn the docs only

Pulls a list of your PDF documents from HEU on demand, instead of waiting for a trigger to spot them. Useful for a one-off pass over what already exists.

When to use it
when a scenario started by another app needs to look through existing documents, for an audit or an export.
Watch out
a long list means many bundles and many operations downstream, so filter early when you can.
HEU8

Make an API call

ActionIn the docs only

Reaches any endpoint of the HEU API from your scenario, using the same connection as the other modules. It covers what the nine named modules leave out.

When to use it
when you need an HEU feature that none of the listed modules offers.
Watch out
you have to know the HEU API yourself, and Make's HEU page offers little help here since its documentation is limited.
HEU9

Send a signature reminder for a PDF document

ActionIn the docs only

You get the signature follow-up done without writing a single message: the module sends a reminder for a PDF document that is still waiting. It turns a stalled contract into a nudge.

When to use it
when a deal moves to a closing stage in your CRM and the contract is still unsigned.
Watch out
Make does not say who receives the reminder, so run your first test on a document of your own.
Need help

Need help automating HEU with Make?

A person reads every message.

FAQ

HEU and Make: common questions

01Is the HEU Make integration free?
Yes, HEU is a standard app in Make, so it is available on the Free plan. The Free plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the shortest interval to 1 minute, remove the cap on active scenarios and count usage in operations per month. Your HEU subscription itself is a separate matter handled with HEU.
02What do you need to connect HEU to Make?
An HEU account and a Make account are the starting point. Make's HEU documentation lists no prerequisites and is marked as limited, so the connection follows the generic Make steps: add an HEU module, click Create a connection, optionally name it, then authorize Make on the HEU page or paste the key HEU provides, and click Save. The same connection is then reused by every HEU module in your scenarios, so you only do this once per account.
03Does the HEU trigger in Make react in real time?
No. Watch documents is a scheduled trigger, marked with a clock badge in the editor. Make checks HEU on the scenario's schedule rather than being called by HEU the moment something changes. A new scenario runs every 15 minutes by default. On the Free plan 15 minutes is also the shortest gap allowed, while paid plans go down to 1 minute. If you need a faster reaction, start the scenario from another app with an instant trigger and use HEU modules as the actions.
04What if an HEU module is missing in Make?
Use Make an API call. It calls any endpoint of the HEU API with the connection you already set up, so you are not limited to the ten listed modules. Keep in mind that Make's HEU help page is flagged as limited documentation, with no field list and no module descriptions. You will need the HEU API reference on hand, and a Run once test on each step is the safest way to see what a module expects and what it returns.
05Should you use Make or n8n for HEU?
It depends on what the rest of your stack runs on. In Make, HEU brings ten modules: one scheduled trigger, five actions and four searches, plus the API call module for the gaps. Many apps also exist as an n8n node, so check whether HEU has one before you decide, then compare the two on the exact operations you need, such as creating PDF documents or chasing signers. Test the modules you plan to use on both sides before you commit, since this page makes no claim on how the two compare.
Same platform

Other docs you might need on this stack.

Browse all integrations