Resources · Make integration

D4Sign Make integrationAutomate D4Sign with Make.

Contracts that leave for signature on their own, straight from your other tools. The D4Sign Make integration gives you 26 action modules, from template generation to signer management. This guide shows how to connect your account and build a first scenario step by step.

Try the D4Sign integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the D4Sign Make integration do for you?

The D4Sign Make integration links your D4Sign account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Each step is a module, one brick of that chain. D4Sign brings 26 of them, all actions: they create, send, fetch or update documents when an earlier step hands them data.

Contracts built from your sales data. A deal closes in your CRM, Gerar documento de template turns it into a contract, Adicionar signatários puts the client on it and Enviar para assinatura sends it. Nobody copies a name by hand.

Signed files where your team works. Baixar documento pulls the file out of D4Sign so a later module can file it in your storage app, and Criar ou atualizar pasta keeps the D4Sign side tidy too.

A clean house. Listar documentos, Listar cofres and Listar tags do documento let a scenario read what sits in your account before it acts, and Cancelar documento withdraws a contract that should not go out.

Two limits to know. D4Sign has no trigger in Make, so something else has to start the scenario: a schedule or another app. And Make says its own D4Sign documentation is limited, so plan a test run for every module you add. When a listed module falls short, Make an API call reaches the rest of the D4Sign API with the same connection.

The same app often exists in n8n as well; the n8n vs Make comparison helps you pick. New to the tool? Start with the Make review, or ask the Make agency to set it up with you.

Connect

How do you connect D4Sign to Make?

  1. 01

    Add a D4Sign module

    Open your scenario, click the +, type D4Sign and pick any of its modules. Then click Create a connection. A connection is your D4Sign account linked to Make once and reused by every D4Sign module after that.

  2. 02

    Name the connection

    This part is optional but handy. Give the connection a name you will recognize later, such as the account owner or the team it belongs to, so nobody picks the wrong account when several people share Make.

  3. 03

    Authorize and save

    Follow what D4Sign asks for: approve Make on its authorization page, or paste the key D4Sign gives you. Click Save. Make can now read your D4Sign data and show it in the module fields.

First scenario

Your first scenario with D4Sign in Make

GoalWhen a deal is won in your sales tool, Make generates the D4Sign contract from a template and sends it for signature.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where deals are closed and its trigger, the module that starts the whole chain.

  2. 02

    Add the contract step

    Click the + on the right of the trigger, search D4Sign and choose Gerar documento de template. Create the connection, then pick your template in the list Make shows.

  3. 03

    Map the deal data

    Fill the template fields with values from the trigger: client name, amount, date. Each deal arrives as a bundle, one item passed from module to module, so every contract gets its own data.

  4. 04

    Send it for signature

    Add Enviar para assinatura and map the document produced by the previous module. The contract now leaves D4Sign without anyone opening it.

  5. 05

    Test, then switch on

    Click Run once with a test deal and read the bundles each module received. When it looks right, set the schedule on the first module (every 15 minutes by default) and turn the scenario on.

Modules

The 26 D4Sign modules in Make

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

D4Sign1

Adicionar ou remover posições de assinatura

ActionIn the docs only

Your generated contract arrives with its signature spots already placed, or cleared. The Portuguese name reads "add or remove signature positions", the boxes where each signer signs.

When to use it
right after a document lands in D4Sign and before it goes out, when the layout changes from one contract model to another.
Watch out
the Make doc for D4Sign is thin, so run it on a test file and look at the result in D4Sign.
D4Sign2

Adicionar ou remover tags de documento

ActionIn the docs only

Keeps documents easy to find later by putting tags on them or taking tags off. The name means "add or remove document tags", the labels you filter on inside D4Sign.

When to use it
a deal moves to a new stage in your CRM and the matching contract should carry the new label.
Watch out
read the current labels first with Listar tags do documento if the scenario needs to know what is already there.
D4Sign3

Adicionar signatários

ActionIn the docs only

Puts the right people on a document: this module adds signers (signatários) to a file already stored in D4Sign, with the details mapped from an earlier module.

When to use it
a new client appears in your CRM and the contract needs that client as signer.
Watch out
if the signers reach the module as separate bundles, each one is a separate operation, and operations are what Make counts on your plan.
D4Sign4

Atualizar observadores de documento

ActionIn the docs only

Changes who is kept in the loop on a document. Observadores means observers: as the word suggests, people attached to a file who watch it rather than sign it.

When to use it
an account manager takes over a client and should follow that client's pending contracts.
Watch out
updating can replace the current list, so check it first with Listar observadores de documento and run a test on one document.
D4Sign5

Atualizar signatário

ActionIn the docs only

Fixes a signer who is already on a document instead of starting over. Atualizar signatário means "update signer": a typo in an email or a change of contact person gets corrected in place.

When to use it
a contact record changes in your CRM while a contract with that person is still open.
Watch out
you usually need to know which signer to edit, so place Buscar signatários do documento before it.
D4Sign6

Baixar documento

ActionIn the docs only

Gets the D4Sign file into your scenario so another app can keep a copy. Baixar documento means "download document"; the file then travels to the next module as data you can map.

When to use it
a signed contract should be filed in the drive or the CRM record where your team actually looks.
Watch out
on the Free plan, Make handles files up to 5 MB, so try your heaviest scanned contract in a Run once first.
D4Sign7

Buscar documento

ActionIn the docs only

Finds one document and hands its details to the next step. Buscar documento means "fetch document", the move you make when the scenario knows which contract it wants but not its current state.

When to use it
before downloading, tagging or cancelling a file, to confirm it exists and to read what D4Sign stores about it.
Watch out
it is typed as an action, not a search, so treat it as one lookup per bundle rather than a list.
D4Sign8

Buscar signatários do documento

ActionIn the docs only

Shows who is set to sign a given document, so your scenario can react to the actual list instead of guessing. The name reads "fetch the document's signers".

When to use it
ahead of Atualizar signatário, or to send a friendly reminder through your email app to the people named on a contract.
Watch out
a contract can have several signers, so check in Run once whether they come back as one bundle or several.
D4Sign9

Buscar um grupo de assinatura

ActionIn the docs only

Pulls up a signature group, a saved set of signers you reuse, so the scenario can work with it without retyping anyone. The name means "fetch a signature group".

When to use it
the same directors sign every supplier contract and you want the scenario to confirm that group before sending.
Watch out
judging by the name of Listar grupos do cofre, groups sit inside vaults, and that module is the easier way to see which ones exist.
D4Sign10

Cancelar documento

ActionIn the docs only

Withdraws a contract so it can no longer be signed. Cancelar documento means "cancel document", the clean exit when a deal falls through after the file went out.

When to use it
a deal is marked lost in your CRM while its contract is still waiting for signatures.
Watch out
treat a cancellation as final; add a filter before this module and test it on a dummy document, never on a live one.
D4Sign11

Criar ou atualizar pasta

ActionIn the docs only

Gives each client or project its own folder in D4Sign, and renames it when things change. The name reads "create or update folder", so one module covers both cases.

When to use it
a new customer signs up and every future contract for that customer should land in the same place.
Watch out
judging by Listar pasta do cofre, folders live inside a vault, so find the right one with Listar cofres or Listar pasta do cofre first.
D4Sign12

Enviar anexo

ActionIn the docs only

Adds a supporting file to an existing document, so the signer sees everything in one place. Enviar anexo means "send attachment": a price sheet, a set of terms, an ID copy.

When to use it
the main contract comes from a template and the annexes come from another app, such as a drive folder.
Watch out
the Free plan caps files at 5 MB, and the doc gives no D4Sign-side limit, so test with your heaviest annex.
D4Sign13

Enviar documento

ActionIn the docs only

Uploads a ready-made file into D4Sign, which is how a PDF built elsewhere becomes a document you can sign. Enviar documento means "send document", sent to D4Sign here, not to a signer.

When to use it
your contracts are produced by another tool and D4Sign only handles the signing part.
Watch out
uploading is not sending for signature; Enviar para assinatura is the separate module that does that.
D4Sign14

Enviar para assinatura

ActionIn the docs only

This is the step that puts a contract in front of its signers. Enviar para assinatura means "send for signature", and it usually comes last, once the file, signers and positions are set.

When to use it
the document has been generated or uploaded and everything on it is final.
Watch out
signers get the request as soon as it runs, so point your Run once tests at a test contract with your own address.
D4Sign15

Gerar documento de template

ActionIn the docs only

Produces a filled-in contract from one of your D4Sign templates, with the blanks completed by data from earlier modules. The name means "generate document from template".

When to use it
your contracts follow a fixed model where only the client, amounts and dates change.
Watch out
once the connection exists, Make lists what it can read, so pick the template from the list rather than typing an ID by hand.
D4Sign16

Listar cofres

ActionIn the docs only

Returns the vaults (cofres) of your account, the top-level spaces where D4Sign keeps folders and documents. Handy to see the structure before anything else runs.

When to use it
first test after connecting, or at the start of a scenario that must pick a vault by name.
Watch out
several vaults can come back, and every module placed after it runs once per bundle, which adds operations.
D4Sign17

Listar documentos

ActionIn the docs only

Gives your scenario an inventory of the documents in D4Sign, ready to be checked, tagged or copied elsewhere. Listar documentos means "list documents".

When to use it
a scheduled scenario that reviews pending contracts and posts a summary to your team chat.
Watch out
a long list means many bundles, and each module after it counts one operation per bundle on your plan.
D4Sign18

Listar grupos do cofre

ActionIn the docs only

Shows the signature groups saved in one vault, so you know which reusable sets of signers exist before you use one. The name reads "list the vault's groups".

When to use it
building a scenario that picks a group by department and wants to avoid a hardcoded choice.
Watch out
you point it at a vault, so run Listar cofres before it if you are unsure which vault holds the groups.
D4Sign19

Listar observadores de documento

ActionIn the docs only

Reads who is following a document as an observer, handy for auditing who sees what. Listar observadores de documento means "list document observers".

When to use it
before you update observers, or when a scenario must tell a manager which colleagues follow a sensitive contract.
Watch out
an empty result is normal on documents nobody added observers to, so add a filter after it.
D4Sign20

Listar pasta do cofre

ActionIn the docs only

Opens a vault and lists its folders, which lets the scenario choose where a new contract belongs. The name means "list vault folder".

When to use it
ahead of Criar ou atualizar pasta, to check whether a client folder is already there.
Watch out
the doc does not say whether it also goes into subfolders, so compare the output of a Run once with what you see in D4Sign.
D4Sign21

Listar posições de assinatura

ActionIn the docs only

Tells you where signatures are placed on a document, which is how you catch a missing box before the file goes out. The name reads "list signature positions".

When to use it
a checking step between Adicionar ou remover posições de assinatura and Enviar para assinatura.
Watch out
positions are per document, so feed it the document from the previous module, not a fixed value.
D4Sign22

Listar tags do documento

ActionIn the docs only

Reads the labels already set on a document, which lets a scenario branch on them. Listar tags do documento means "list document tags".

When to use it
to skip contracts tagged as handled, or to copy a tag into a column of your tracking sheet.
Watch out
tag names must match exactly in the filter that follows, so copy them from a Run once result.
D4Sign23

Make an API call

ActionIn the docs only

Reaches any endpoint of the D4Sign API from your scenario, using the connection you already created. It is the way out when none of the other D4Sign modules does what you need.

When to use it
a D4Sign feature exists in the API but has no ready-made module in Make.
Watch out
you write the request yourself, so keep the D4Sign API reference at hand and test with Run once.
D4Sign24

Monitorar eventos de documentos

ActionIn the docs only

Despite a name that reads "monitor document events", the module list types it as an action, not a trigger, so it runs when the scenario reaches it rather than starting the scenario.

When to use it
inside a scenario already started by a schedule or another app, when you want D4Sign's events on documents.
Watch out
the doc is limited here; run it once and read the bundle to see what it returns.
D4Sign25

Obter saldo conta

ActionIn the docs only

Brings back your D4Sign account balance, so a scenario can warn someone before the account runs short. Obter saldo conta means "get account balance".

When to use it
a small scheduled scenario that posts the balance to a finance channel or a sheet.
Watch out
the doc does not say what the balance is counted in, so read the bundle from a Run once before you build a threshold on it.
D4Sign26

Registrar webhook em documento

ActionIn the docs only

Asks D4Sign to call a web address when something happens to a given document. A webhook is that call; the name means "register a webhook on a document".

When to use it
you already have a URL waiting for D4Sign notices and want each new contract wired to it.
Watch out
it is typed as an action, not an instant trigger, so registering does not by itself start this scenario.
Need help

Need help automating D4Sign with Make?

A person reads every message.

FAQ

Questions about D4Sign and Make

01Is the D4Sign Make integration free?
Yes, you can use it on the Free plan, because D4Sign is a standard app in Make and not an Enterprise one. The Free plan has limits you will feel quickly: 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 interval to 1 minute and allow unlimited active scenarios. Your D4Sign subscription is a separate matter.
02What do you need to connect D4Sign to Make?
A D4Sign account and a Make account. The Make documentation lists no other prerequisite for D4Sign. You add any D4Sign module, click Create a connection, name it if you like, then either approve Make on the D4Sign page or paste the key D4Sign gives you, and click Save. Every D4Sign module in your scenarios reuses that same connection afterwards. Test it right away with a read-only module such as Listar cofres to confirm Make sees your account.
03Does the D4Sign Make integration have a real-time trigger?
No. D4Sign has no trigger module in Make at all, instant or scheduled: its 26 modules are all actions. A D4Sign scenario therefore starts in one of two ways. Either another app's trigger opens it, for example a deal won in your CRM, or you start it with a schedule set on the first module, every 15 minutes by default and never under 15 minutes on the Free plan. Monitorar eventos de documentos and Registrar webhook em documento are actions too, so they do not start a scenario.
04What if a D4Sign module is missing in Make?
Use Make an API call. It reaches any endpoint of the D4Sign API from the scenario, with the connection you already have, so a feature without its own module is still within reach. Make also warns that its D4Sign documentation is limited, for lack of public information on the app. Plan a Run once on every module you add, read the bundles it returns and check the result in D4Sign before switching the scenario on.
05Should you use Make or n8n for D4Sign?
It depends on what you check first. In Make, D4Sign comes with 26 modules covering templates, signers, folders and sending, plus Make an API call for the rest, and you can try all of it on the Free plan. The same app often has an n8n node too, so compare the actions each tool offers for D4Sign against your own process. Neither choice is better by default; pick the tool whose modules match the steps you need and that your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations