Resources · Make integration

ForSign Make integrationAutomate ForSign with Make.

Can Make drive ForSign for you, without a line of code? The ForSign Make integration adds 3 action modules and no trigger. This guide is for teams already on ForSign: link your account, then build and test a first scenario, one click at a time.

Try the ForSign integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ForSign Make integration let you automate?

The ForSign Make integration links your ForSign account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as an action on one app. ForSign brings three action modules, so another app or a schedule starts the flow and ForSign does its part next.

Start with the names. Criar Operação and Enviar Documento are Portuguese labels, which read as “create operation” and “send document”. The documentation gives no description for them, so treat those translations as a hint and open each module to read its real fields before you rely on it.

A sales team could place Criar Operação right after a module from its CRM, so a won deal feeds ForSign without anyone retyping the client. An HR team could chain Criar Operação and Enviar Documento behind an onboarding form. For anything the named modules do not cover, Universal is the third brick to inspect.

Know the limits before you build. Make itself states that its ForSign documentation is limited because public information about the app is scarce. There is no trigger, so ForSign cannot start a scenario, and there is no Make an API Call module either. When you get stuck, the Make troubleshooting guide helps, and Make training covers the editor basics.

Still weighing tools? The n8n vs Make comparison lays out the criteria without picking a winner for you.

Connect

How do you connect ForSign to Make?

  1. 01

    Add a ForSign module

    In your scenario, click the +, search for ForSign and pick any of its three modules. Then click Create a connection. A connection is your ForSign account linked to Make once and reused by every ForSign module afterwards.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when several accounts sit side by side. Then either approve Make on the ForSign page that opens, or paste the key ForSign gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. From now on, the module can read what your account exposes, and Make fills its lists for you when fields offer choices. If the save fails, check the key or sign in again.

First scenario

Your first scenario with ForSign

GoalWhen an event happens in another app, Make runs Criar Operação and then Enviar Documento in ForSign.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Since ForSign has no trigger, that first brick comes from another app, such as your CRM or form tool.

  2. 02

    Add Criar Operação

    Click the + on the right of the first module, search ForSign and choose Criar Operação. Pick your connection, then fill its fields, mapping data from the module before it.

  3. 03

    Chain Enviar Documento

    Add Enviar Documento with the next +. Map what the earlier modules return wherever a field asks for it. Unsure what a field expects? Map your best guess and let the test show you.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, a bundle being one item passed along. Check them in ForSign too.

  5. 05

    Schedule and switch on

    Open Scheduling on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go lower. Pick your interval and switch the scenario on.

Modules

What the ForSign modules do

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

ForSign1

Criar Operação

ActionIn the docs only

This action opens the flow on the ForSign side. Its Portuguese name reads as “create operation”, and it is the natural first ForSign step of a scenario, since the app has no trigger to begin with.

When to use it
right after the module that brings in your new client or deal, so the record reaches ForSign without copy and paste.
Watch out
the doc describes none of its fields, so run it once and read the output bundle before chaining anything.
ForSign2

Enviar Documento

ActionIn the docs only

Enviar Documento, “send document” in Portuguese, is the ForSign action you place after the data is ready. Treat the name as a clue rather than a promise, and check in ForSign what actually changes when it runs.

When to use it
as the closing module, once the earlier steps have produced everything its fields ask for.
Watch out
each run counts as an operation on your Make plan, so test with Run once on a single bundle first.
ForSign3

Universal

ActionIn the docs only

Universal is the third ForSign action, and the only one whose name says nothing about its job. Open it in the editor and look at the fields Make displays: they tell you more than any label here can.

When to use it
when Criar Operação and Enviar Documento do not fit the step you need, and you want to see whether this module covers it.
Watch out
it is not the Make an API Call module, which ForSign lacks, so do not assume it accepts any request.
Need help

Need help automating ForSign with Make?

A person reads every message.

FAQ

ForSign and Make: common questions

01Is the ForSign Make integration free?
Yes, on the Make side. ForSign is a standard app, so its modules work from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your ForSign subscription is a separate matter that this page does not cover.
02What does connecting ForSign to Make require?
A ForSign account. The documentation lists no specific prerequisite, so the generic Make flow applies: add a ForSign module, click Create a connection, optionally name it, then authorize Make on the ForSign page or paste the key ForSign provides, and click Save. The connection is then shared by all three modules. If a key is required and you cannot find it, the ForSign support team is the right place to ask, since Make does not document where it lives.
03Can ForSign start a Make scenario instantly?
No. ForSign has no trigger module in Make, neither scheduled nor instant, so it cannot launch a scenario by itself. Two workarounds exist. You can open the scenario with a trigger from another app, for example the tool where new clients or deals appear, and let ForSign act after it. Or you can let Make start the scenario on its own schedule, every 15 minutes by default, with 1 minute possible on paid plans. In both cases ForSign enters the flow through Criar Operação, Enviar Documento or Universal.
04What if a ForSign module is missing in Make?
It depends on the gap. ForSign offers three actions and no Make an API Call module, so you cannot send a custom request to its API from Make. First open Universal, the least specific of the three, and check whether its fields cover your need. If not, handle that step in another app that holds the same data, or in ForSign directly. Make also notes that its ForSign documentation is limited for lack of public information, so a quick test with Run once tells you more than the doc. The Make agency team can also help you map a workaround.
05Make or n8n for ForSign?
It depends on the tool your team already runs. On Make, ForSign gives you three action modules, no trigger and no generic API module, and it works from the Free plan. Whether an n8n node exists for ForSign is not documented in the sources behind this page, so check the n8n node list before comparing. Then weigh the practical criteria: which tool already hosts your other automations, who will maintain the scenario, and whether the three ForSign modules cover the steps you need. No tool is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations