Resources · Make integration

Hi Sign Make integrationAutomate Hi Sign with Make.

Can Make create and fetch your Hi Sign documents for you? The Hi Sign Make integration gives you 8 action modules for documents and users, and no trigger. This page shows how to link your account and build a first scenario that starts from another app.

Try the Hi Sign integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Hi Sign Make integration do?

The Hi Sign Make integration lets a Make scenario, the automation you build as a chain of modules, act on your Hi Sign account without code. Each module is one brick of that chain. Hi Sign offers 8 of them, all actions: they create, look up, update or download, but none of them starts a scenario on its own.

Signer accounts ready before the paperwork. When a new client lands in your CRM, Consultar um Usuário checks whether that person already exists in Hi Sign, and Criar um Usuário adds them if not. Nobody retypes a name.

Documents that appear where the deal happens. A deal marked as won in another tool can feed Criar um Documento, then Baixar um Documento retrieves the file so a later module can store or send it.

A tidy archive. Pesquisar Documentos finds documents in your account, which helps before you download or report on them.

What Make does not do here: Hi Sign has no trigger, so something else must start the scenario, and the module names stay in Portuguese in the editor. The Hi Sign documentation in Make also warns that it is AI-generated and may contain errors, so test every module with Run once. If you weigh other tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains plans, and the Make training helps you get started.

Connect

How do you connect Hi Sign to Make?

  1. 01

    Get your Hi Sign API key

    You need an active Hi Sign account and an API key. In the Hi Sign dashboard, open the section called API or Integrações, generate a key if none exists yet, and copy it somewhere safe for the next step.

  2. 02

    Add a Hi Sign module

    In your Make scenario, add any Hi Sign module and click Create a connection. The Connection name field is optional; a clear label such as the account owner helps when several people share the workspace.

  3. 03

    Paste the key and save

    Paste the API key you copied from Hi Sign and confirm. The connection, your Hi Sign account linked to Make once, is now reused by every Hi Sign module in all your scenarios.

First scenario

Your first scenario with Hi Sign

GoalWhen a new client arrives in another app, Make creates their Hi Sign user and then a Hi Sign document for them.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Hi Sign has no trigger, pick the module of the app where new clients appear, such as your form or CRM.

  2. 02

    Add Criar um Usuário

    Click the + to the right of that first module, search for Hi Sign and choose Criar um Usuário. Create the connection with your API key, then map the client data coming from the previous module.

  3. 03

    Add Criar um Documento

    Click the + again, choose Criar um Documento and reuse the same connection. Fill its fields with data mapped from the earlier modules so each new client gets a document.

  4. 04

    Test with Run once

    Click Run once and create a test entry in the first app. Each module then shows the bundles it received, one item passed from module to module, so you can check the user and document in Hi Sign.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set Scheduling; a new scenario checks every 15 minutes by default. Then switch the scenario on so it runs without you.

Modules

What the Hi Sign modules do

Hi Sign gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Hi Sign1

Atualizar um Usuário

ActionIn the docs only

Keeps a Hi Sign user in line with your other tools: the name translates as Update a User, and it changes a person who already exists in your account.

When to use it
a client changes their details in your CRM and the matching Hi Sign user should follow without anyone editing it by hand.
Watch out
it acts on one existing user, so place Consultar um Usuário before it to target the right person.
Hi Sign2

Baixar um Documento

ActionIn the docs only

Brings a Hi Sign document into your scenario as a file, so a later module can store it, attach it or send it elsewhere. The name means Download a Document.

When to use it
once a contract is finished in Hi Sign and your team wants a copy in shared storage.
Watch out
on the Free plan Make handles files up to 5 MB, so large documents can stop the run.
Hi Sign3

Consultar um Usuário

ActionIn the docs only

Reads one Hi Sign user so the rest of the scenario can rely on their details instead of guessing. In English, the name reads Look Up a User.

When to use it
before creating someone, to avoid a duplicate, or before an update, to confirm you hold the right person.
Watch out
the documentation gives no field details, so run it once and inspect the bundle it returns before mapping anything.
Hi Sign4

Criar um Documento

ActionIn the docs only

Opens a new document in Hi Sign from data your scenario already holds, which removes the copy and paste step between your sales tools and your signing tool.

When to use it
right after a deal is won or a form is submitted, so the paperwork starts from the same event.
Watch out
each run creates one more document, so test with Run once on sample data before switching the scenario on.
Hi Sign5

Criar um Usuário

ActionIn the docs only

Adds a new person to your Hi Sign account from another app, so a signer or colleague exists before any document needs them. The name means Create a User.

When to use it
when a new client or employee is registered elsewhere and should also have a Hi Sign profile.
Watch out
run Consultar um Usuário first when the same person may arrive twice, or you risk creating a duplicate.
Hi Sign6

Fazer uma chamada API

ActionIn the docs only

Gives you a way to reach a Hi Sign function that none of the other named modules covers. The name is Portuguese for doing an API call, and it belongs to the Hi Sign app itself.

When to use it
only after checking that the other seven modules cannot do the job.
Watch out
Make's documentation describes nothing about this module, so expect to rely on Hi Sign's own API guidance and test with Run once.
Hi Sign7

Pesquisar Documentos

ActionIn the docs only

Finds documents in your Hi Sign account so you can work on existing files rather than new ones. The name means Search Documents.

When to use it
ahead of Baixar um Documento, when you need to locate the right contract before fetching it, or to gather documents for a report.
Watch out
Make lists it as an action, not a search, so check with Run once how many bundles it actually passes on.
Hi Sign8

Webhook

ActionIn the docs only

Despite its name, this Hi Sign module is listed as an action, so it runs inside a scenario that something else has already started and never starts one itself.

When to use it
only when your Hi Sign setup calls for it and you know what it should do in your account.
Watch out
the documentation says nothing about its behavior, so try it on a test scenario with Run once before relying on it.
Need help

Need help automating Hi Sign with Make?

A person reads every message.

FAQ

Hi Sign and Make: common questions

01Is the Hi Sign Make integration free?
Yes, Hi Sign is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. Each operation is one module running on one bundle. Your Hi Sign subscription is a separate matter handled by Hi Sign.
02What do you need to connect Hi Sign to Make?
You need an active Hi Sign account and an API key from it. In Hi Sign, the key sits in the section called API or Integrações; generate one if the list is empty and copy it. Then add any Hi Sign module in Make, click Create a connection, optionally name it, and paste the key. The connection is stored once and every Hi Sign module in your scenarios reuses it, so you do not repeat the step for each module.
03Does Hi Sign trigger Make scenarios in real time?
No, because the Hi Sign app has no trigger at all: its 8 modules are actions. To start a scenario anyway, put another app's trigger first, for example the tool where your clients or deals appear, and add Hi Sign modules after it. The other option is to start with a Hi Sign module and rely on the scenario schedule, which runs every 15 minutes by default and can be changed on the clock of the first module. How fast things happen then depends on that first app or on the schedule you set.
04What if a Hi Sign module is missing in Make?
It depends on what you need. Hi Sign has no universal Make an API Call module, so do not count on one. The app does include a module named Fazer uma chamada API, but Make's documentation does not describe it, so test it with Run once before building on it. The same documentation is flagged as AI-generated and possibly wrong, which is worth keeping in mind. If the gap remains, another app may cover the step, or the Hackceleration team can review the scenario with you.
05Should you use Make or n8n for Hi Sign?
It depends on your criteria rather than on a winner. On Make, Hi Sign offers 8 modules covering users and documents, runs on the Free plan and connects with a single API key, which suits someone who wants to start from the visual editor. Many apps also have an n8n node, so check whether Hi Sign has one and which actions it covers before choosing. Compare the modules each tool offers, how the account connects and what your team already uses, then pick the tool that fits those needs.
Same platform

Other docs you might need on this stack.

Browse all integrations