Resources · Make integration

Signority Make integrationAutomate Signority with Make.

Can Make pick up your Signority documents and move them along for you? Yes. The Signority Make integration gives you 7 modules: one scheduled trigger, four actions and two searches. This page walks an ops or sales lead through the connection, a first scenario and every module.

Try the Signority integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Signority Make integration do?

The Signority Make integration links your Signority account to Make so documents can start or feed a scenario, the automation you build as a chain of modules. A module is one brick of that chain: a trigger that starts things, an action that does something, or a search that looks things up.

Paperwork that starts itself. A new deal lands in another tool, and Create a Document opens the matching Signority document without anyone retyping the details.

A log of every new document. Watch New Documents notices each document added to the account, then List Files tells you what is inside it, ready to copy into a sheet or a message for the team.

Housekeeping on request. List Documents finds what matches, and Delete File of a Document removes a file you no longer want to keep. Handle that one with care, since a deletion is hard to take back.

Know the limits before you start. Signority offers seven modules, and the trigger is scheduled, so Make checks for new documents on the scenario's clock rather than the moment they appear. Anything the modules skip goes through Make an API Call. The Make documentation page for Signority is itself AI-generated, so double-check important details with Signority. If you want a second opinion on the tool, read the Make review, and the n8n vs Make comparison helps if you also weigh n8n. Teams who prefer a hand can look at the Make training.

Connect

How do you connect Signority to Make?

  1. 01

    Grab your API key in Signority

    A connection is your Signority account linked to Make once and reused by every Signority module. In Signority, open My Account, then Profile Settings, then Integration, and copy the API key shown on screen.

  2. 02

    Add a Signority module in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the on-screen instructions, then confirm. From then on, every Signority module in your scenarios can pick this connection from its list.

First scenario

Your first scenario with Signority

GoalWhen a new document appears in Signority, Make lists the files it contains so you can pass them to the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add its first module. An empty canvas is normal at this point.

  2. 02

    Add Watch New Documents

    Search for Signority, pick Watch New Documents, then click Create a connection and paste your API key. This module starts the scenario each time a new document shows up.

  3. 03

    Add List Files

    Click the + on the right of the trigger and choose List Files. Map the document from the previous module so Make knows which document to open.

  4. 04

    Test with Run once

    Click Run once and add a document in Signority if none is waiting. Each module then shows the bundles it received, one item per document or file, so you can check the data.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What can start a Signority scenario?

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

Signority1Watch New Documents

Watch New Documents

Scheduled trigger

In Make“Triggers when a new document is added.”

Watch New Documents gives you a starting point every time a document is added to your Signority account, so the rest of the scenario can act on it without a manual export. Each new document arrives as its own bundle, the single item that flows from one module to the next.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a document waits until the next check.
When to use it
you want a sheet, a chat channel or another app to hear about fresh Signority documents.
Watch out
each check counts as an operation, one execution Make bills on your plan.
Modules

What can Make do in Signority?

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

Signority1

Create a Document

Action

In Make“Creates a document.”

Create a Document opens a new Signority document from data that lives elsewhere, so the details typed in your CRM or a form reach Signority without copy and paste.

When to use it
a deal is marked won in another app and its paperwork should exist right away.
Watch out
pair it with Watch New Documents carefully, or the new document can start the scenario again.
Signority2

Delete File of a Document

Action

In Make“Deletes file of a document.”

Delete File of a Document removes one file attached to a Signority document, which keeps a document tidy when an outdated attachment should no longer travel with it.

When to use it
a draft file was replaced and the older version must disappear from the document.
Watch out
a deletion cannot be undone from Make, so test it on a throwaway document with Run once first.
Signority3

Get a Document

Action

In Make“Gets a document.”

Get a Document fetches one Signority document you already know, and hands its details to the following modules so they can reuse them in a message, a sheet or another app.

When to use it
you have the document from an earlier step and need its full details, not a list.
Watch out
it reads a single document; to look across several, reach for List Documents instead.
Signority4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any part of the Signority API that the six other modules leave out, using the same connection, so a missing module rarely blocks a project.

When to use it
the Signority API offers something you need and no listed module covers it.
Watch out
you write the request yourself, so keep the Signority API documentation open and test the call with Run once.
Signority5

List Documents

Search

In Make“Gets a list documents.”

List Documents returns the documents in your Signority account as separate bundles, which gives you a batch to count, filter or copy into a report without opening each one.

When to use it
you want a snapshot of existing documents rather than only the new ones the trigger catches.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle.
Signority6

List Files

Search

In Make“Gets list of files in document.”

List Files shows what sits inside one Signority document, one bundle per file, so you can see every attachment before sending it on or deciding to clean it up.

When to use it
right after Watch New Documents, to check the contents of the document that just arrived.
Watch out
the module needs a document to look into, so map one from an earlier step.
Need help

Need help automating Signority with Make?

A person reads every message.

FAQ

Questions about the Signority Make integration

01Is the Signority Make integration free?
Yes, on the Make side. Signority is a standard app, so it works on the Free plan, which allows 2 active scenarios, a 15 minute minimum gap 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) bring the gap down to 1 minute and remove the cap on active scenarios. On the Signority side, you still need an active account with an API plan, which Signority prices on its own page.
02What does it take to connect Signority to Make?
An active Signority account with an API plan, plus your API key. You find the key in your Signority account settings, under Profile Settings, then Integration. In Make, add any Signority module, click Create a connection, give the connection a name if you like, and paste the key. The connection is saved once and every Signority module in your scenarios can reuse it. If the key is refused, check that your Signority subscription includes API access.
03Does the Signority trigger work in real time?
No. Watch New Documents is a scheduled trigger: Make asks Signority for new documents on the scenario's schedule, which is every 15 minutes by default. On the Free plan that is also the shortest gap. Paid plans let you go down to 1 minute. Signority has no instant trigger in Make, so a document added just after a check waits for the next one. Each check counts as an operation on your plan.
04What if a Signority module is missing in Make?
Use Make an API Call. It calls any endpoint of the Signority API with the connection you already set up, so it covers what the seven listed modules do not. You write the request yourself, based on the Signority API documentation. Keep in mind that the Make documentation page for Signority is AI-generated and may contain mistakes, so confirm important details with Signority before building a scenario on top of them.
05Is Make or n8n better for Signority?
It depends on the tool your team already uses. Signority works in Make with 7 modules, including a scheduled trigger and a Make an API Call module for anything else, and the same app often has an n8n node too. Compare the modules each side lists for Signority against the job you have in mind, then pick the editor your team is comfortable in. A side by side comparison of both tools is linked from this page.
Same platform

Other docs you might need on this stack.

Browse all integrations