Resources · Make integration

Signi Make integrationAutomate Signi with Make.

Can a contract build itself the moment a deal is ready? The Signi Make integration gives you 10 modules, 8 actions and 2 searches, to create, fetch and file contracts without code. This guide connects your account and walks you through a first working scenario.

Try the Signi integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Signi Make integration let you automate?

The Signi Make integration links your Signi account to Make, a no-code tool where you build a scenario: a chain of steps that runs on its own. Each step is a module, one brick that creates, reads or deletes something. Here, every brick works on contracts and templates, so paperwork gets drafted and archived without copy and paste.

Drafts that write themselves. A sales team closes a deal in its CRM, and Create a Contract from Template turns the client details into a Signi contract. Want to check the wording first? Create a Contract Preview from Template returns an HTML preview built from the same data.

A clean archive. An office manager pairs Download a PDF with a storage app so each contract lands in the right client folder, and Get a Contract Revision List adds the PDF of its history next to it.

Reporting on demand. List Contracts pulls every contract of the account, or only those of one counterparty, into a sheet your legal team reads.

Know the limits. Signi has no trigger in Make, so a scenario starts from another app or from a schedule. The Signi documentation on Make also warns that it was generated by AI from Signi's own docs and may contain mistakes. Before you pick a tool, the n8n vs Make comparison sets out the criteria, Make pricing explains how operations are counted, and Make training helps if your first scenario grows fast.

Connect

How do you connect Signi to Make?

  1. 01

    Generate an API key in Signi

    In Signi, click the API button on the left side of the screen and type your password when asked. Pick the workspace the key should cover, click Generate new API key, then copy the key shown.

  2. 02

    Add a Signi module in Make

    Log in to Make, open your scenario and add any Signi module. Click Create a connection. A connection is your Signi account linked to Make once, then reused by every Signi module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear name in Connection name if you like, which helps when you run several workspaces. Paste the API key you copied from Signi, follow any on-screen instructions, and save.

First scenario

Build your first scenario with Signi

GoalWhen a new answer lands in your form app, Make creates a Signi contract from your template.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Signi has no trigger, so this first bubble comes from the app that holds your client data, such as a form.

  2. 02

    Set the starting module

    Search your form app by name, pick its module for new entries and click Create a connection. Each entry becomes a bundle, one item passed from one module to the next.

  3. 03

    Add Create a Contract from Template

    Click the + on the right, search Signi and choose Create a Contract from Template. Once your connection exists, Make can list what it reads from Signi; map the form answers into the template.

  4. 04

    Test with Run once

    Submit a test entry, then click Run once. Open the bundles each module received to confirm the contract was built with the right name and details before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default for a new scenario, then switch the scenario on. Each module run on one bundle counts as an operation on your plan.

Modules

What each Signi module does

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

Signi1

Create a Contract from Document

Action

In Make“Creates a contract from a document with optional attachments.”

Turns a document you already have, such as a file drafted by your lawyer, into a Signi contract, with extra attachments if the deal needs them.

When to use it
your contract text changes from one client to the next, so a fixed template would not fit.
Watch out
the document has to reach this module from an earlier one, for example a storage app, such as a storage app that fetches the file.
Signi2

Create a Contract from Template

Action

In Make“Creates a contract from a template with optional attachments.”

Fills one of your Signi templates with data from earlier modules and produces a finished contract, attachments included when you add them. It is the workhorse for repeat agreements.

When to use it
every new client signs the same agreement and only the names, amounts or dates change.
Watch out
run List Templates once to see which template you are pointing at before you map anything.
Signi3

Create a Contract Preview from Template

Action

In Make“Creates a (partly) filled template and returns an HTML preview of the contract.”

Builds a partly or fully filled template and hands back an HTML preview instead of a real contract. You read the wording before you create the real contract.

When to use it
a manager wants to approve the wording, so you send the preview by email or chat first.
Watch out
the result is HTML, so route it to a module that can display or send HTML.
Signi4

Delete a Contract

Action

In Make“Deletes a contract specified by ID.”

Removes the contract whose ID you give it, which is handy to clear out test contracts or the drafts a cancelled deal left behind.

When to use it
a deal is lost in your CRM and the matching draft should disappear from Signi too.
Watch out
it deletes whatever ID you map. Check that ID with Get a Contract before letting the scenario run alone.
Signi5

Download a PDF

Action

In Make“Retrieves a PDF of a contract specified by ID.”

Fetches the PDF of a contract from its ID, ready to pass to a storage, email or accounting app in the next module.

When to use it
finance wants a copy of each contract in the shared drive without asking anyone to export it by hand.
Watch out
on the Free plan Make handles files up to 5 MB, so keep an eye on contracts that carry heavy attachments.
Signi6

Get a Contract

Action

In Make“Returns details about a contract specified by ID.”

Returns the details Signi holds about one contract, identified by its ID, so later modules can reuse them.

When to use it
you stored a contract ID in a sheet or CRM and now need its current details to update that record.
Watch out
it needs an exact ID; if you only know the client, start with List Contracts and filter the results.
Signi7

Get a Contract Revision List

Action

In Make“Retrieves a PDF with the contract history.”

Despite its name, this module gives you a PDF that traces the history of a contract, not a table of rows. That file serves as a record of what happened to the document.

When to use it
your compliance team keeps a trail next to every signed contract in its archive.
Watch out
treat the output as a file and send it to a storage module rather than a spreadsheet.
Signi8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request of your choice to the Signi API, reusing the connection you already set up. It covers whatever the nine other modules leave out.

When to use it
you need an action Signi offers in its API that no listed module exposes.
Watch out
you write the request yourself, so keep the Signi API documentation open and test the call with Run once.
Signi9

List Contracts

Search

In Make“Retrieves a list of all contracts for the account or a specified counterparty.”

Brings back all contracts in the account, or only the ones tied to a counterparty you name. Each contract arrives as its own bundle.

When to use it
you build a status sheet of every agreement signed with one supplier.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations.
Signi10

List Templates

Search

In Make“Retrieves a list of templates to complete the data and signature.”

Shows the templates available in your workspace, the ones you fill with data before a signature. It saves a trip to the Signi screen when you set up a flow.

When to use it
you want a scenario to pick a template dynamically, for instance by the product a client ordered.
Watch out
templates come from the workspace tied to your API key, so another workspace needs its own connection.
Need help

Need help automating Signi with Make?

A person reads every message.

FAQ

Signi and Make: common questions

01Is the Signi Make integration free?
Yes, on the Make side. Signi is a standard app, available from the Free plan. 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) drop the interval to 1 minute and count usage in credits each month. You still need an active Signi account with API access, whose subscription is described on the Signi pricing page.
02What do you need to connect Signi to Make?
Two things: an active Signi account and an API key. In Signi, click the API button on the left, enter your password, choose the workspace and click Generate new API key. Copy it. In Make, add any Signi module, click Create a connection, name it if you want, and paste the key. The connection then serves every Signi module in your scenarios, so you set it up once per workspace and reuse it everywhere.
03Can the Signi Make integration react in real time?
Not by itself, because Signi has no trigger module in Make. A scenario has to start elsewhere. You can open it with a trigger from another app, such as a form or a CRM, and add Signi modules after it. You can also run it on a schedule set on the first module, every 15 minutes by default, or start it from a webhook provided by Make when another system should call it. Whether the start is instant then depends on that first module.
04What if a Signi module is missing in Make?
Use Make an API Call. It calls any endpoint of the Signi API with the same connection, so an action without its own module stays reachable. Test it with Run once and read the bundle it returns. Keep one caveat in mind: the Signi documentation on Make says it was generated by AI from Signi's documentation and may contain mistakes, so check anything important with Signi, and contact Signi directly for questions about its own docs.
05Should you use Make or n8n for Signi?
It depends on the tool your team already runs. This page covers the 10 Signi modules in Make: 8 actions and 2 searches, plus a connection by API key. An app often has an n8n node too, so check the n8n catalog for Signi before deciding. Neither tool is ranked here. Compare them on what you need: the modules available, how you start a scenario without a Signi trigger, and how each tool counts runs on your plan.
Same platform

Other docs you might need on this stack.

Browse all integrations