Resources · Zapier integration

Modusign Zapier integrationAutomate Modusign with Zapier.

Modusign Zapier integration: 2 triggers, 2 actions, 4 searches. Both triggers are instant, so a signed contract can start a Zap straight away on any plan. Below: what each run costs, how to connect the account, the first Zap to build and what breaks.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Modusign Zapier integration does for you

The Modusign Zapier integration connects your e-signature account to the rest of your tools. Modusign handles signing a contract and storing it in one go; Zapier picks up what happens to each document, sends new ones out from a template, chases late signers and looks documents up. Two triggers, two actions and four searches are on offer, all visible in the editor.

Three results come up most. A log of every closed contract: Document All Signed starts the Zap once all signers are done, Get Document fetches its details, and a spreadsheet gets a new row. A contract sent without opening Modusign: an entry arrives in another tool, and Request Document With Template builds the document from one of your templates and asks the signers to sign. A nudge for whoever has not signed: Remind Signing resends the request to the signers still missing, from the Document ID you pass it.

What Zapier does not do here matters as much. It does not create or edit templates: Request Document With Template only uses a template that already exists in your account. It does not pick up documents signed before your Zap was switched on. And the searches only look things up; none of them can create a missing document for you.

Want to compare before you build? See our n8n vs Zapier guide, or our Make vs Zapier guide.

Vocabulary

The Zapier words you need, in one minute

Zapier comes with its own vocabulary. Each word is explained once here, in plain terms, then used as is on the rest of the page.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a document signed by everyone. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like a signing request.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, as both Modusign triggers are.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a document, so later steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What a Modusign Zap really costs

Modusign is not a premium app, so it works from the free plan. Zapier bills completed actions, never the trigger.

  • Trigger0 tasks
  • Each action that succeeds1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A signed document that starts your Zap costs nothing by itself. Each action that succeeds counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: add a filter, a search such as Get Document, or a second action, and you need a paid plan. The interval grid below applies to polling triggers only. Both Modusign triggers are instant, so it does not apply to them.

Connect

Connect Modusign to Zapier in three steps

  1. 01

    Open the connections page

    In your Zapier account, go to Apps, then click + Add connection. Before you start, have an account on Modusign, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Modusign

    In the dialog, type the app name, select Modusign in the results, then click Add connection. A new tab then opens on the Modusign side for the sign-in.

  3. 03

    Sign in and grant access

    Sign in to Modusign in that tab, then let Zapier use the account. The connection is saved once, and every Modusign step of every Zap you build reuses it.

First Zap

Your first Zap: log every fully signed contract

GoalAdd a row to your spreadsheet each time all the signers of a Modusign document have signed, with the document's details.

  1. 01

    Build: start on Document All Signed

    Create a Zap, pick Modusign as the trigger app and Document All Signed as the event. It is instant, so the Zap starts as soon as the last signer is done, on any plan.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so pick a real signed document to map the next steps on.

  3. 03

    Add Get Document (paid plan)

    Add a search step with Get Document and map the Document ID from the trigger. A search makes the Zap multi-step, so this Zap needs a paid plan.

  4. 04

    Add the spreadsheet row

    Pick your spreadsheet app and its add-a-row action, then map the values Get Document returned into your columns. Read the test output to see which ones are there.

  5. 05

    Test, read, then publish

    Run each step once and read what came back before going further. When the row looks right, click Publish to switch the Zap on.

Triggers

The 2 Modusign triggers

2 events start a Zap when something happens in Modusign, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Document All Signed

Instant trigger

In Zapier“Triggers when all signers have signed.”

Starts your Zap once every signer of a document has signed, and not before. It is the event to watch when only a closed contract should set anything in motion, since partial signatures never start it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a fully signed contract has to be logged, filed or announced to the team, with no step to do by hand once the last signature is in.
Watch out
documents completed before the Zap was published are not picked up, so file the older ones yourself.
2

Document Updated

Instant trigger

In Zapier“Triggers when a document is created, signed, completed, or aborted.”

Goes off at several moments in a document's life: when it is created, signed, completed or aborted. One trigger, four kinds of events, which makes it the broadest view of what happens in your Modusign account.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a status board or a team channel should follow each document from creation to its end, aborted ones included.
Watch out
one trigger covers four kinds of events; check at the test what each run carries, then keep the one you care about with a filter (paid plan).
Actions

The 2 Modusign actions

Modusign gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Remind Signing

Action

In Zapier“Resend signing request notifications to signers who did not sign.”

Sends the signing request notification again, only to the signers who have not signed yet. You give it the Document ID of the document waiting on them.

When to use it
someone flags a pending contract in another tool and the late signers should get a fresh nudge.
Watch out
without a Document ID mapped from an earlier step, there is nothing to remind.
2

Request Document With Template

Action

In Zapier“Create a document using a template and request signers to sign it.”

Builds a new document from one of your Modusign templates and sends it to the signers for signature. It needs the Template ID and a Title for the document.

When to use it
a deal, a booking or a form entry elsewhere should end in a contract to sign, without retyping anything.
Watch out
the template must already exist in the connected account.
Searches

The 4 Modusign searches

4 search steps look for data that already exists in Modusign, so a later step can use it.

A search step looks up something that already exists in Modusign and hands it to the next steps. In the action list of the editor, searches sit at the bottom, under their own heading. Three settings decide what happens when the lookup does not go as planned.

1

Get Document

Search

In Zapier“Get detailed properties of a document.”

Fetches the detailed properties of one document from its Document ID, so later steps can reuse them.

When to use it
the trigger gave you an ID but the row or message you write needs more about the document.
Watch out
the Document ID is required, so map it from the trigger rather than typing it.
2

Get Participants Verification Completed At

Search

In Zapier“Get participants verification completed at.”

Looks up, for the document whose ID you pass, when its participants completed their verification, as the operation's name says.

When to use it
your records need that verification time next to the signed contract.
Watch out
what it returns exactly is worth reading at the test before you map it anywhere.
3

Get Participant Fields

Search

In Zapier“Get participant fields set in the document.”

Reads the participant fields set in a document, starting from its Document ID, and passes them on to the next steps.

When to use it
values the signers filled in should travel to another tool once the document moves on.
Watch out
the fields depend on how the document was set up, so check at the test which ones come back.
4

Search Documents

Search

In Zapier“Search for documents with specific conditions.”

Finds documents that match the conditions you set, without needing an ID first. It is the only Modusign search that does not start from a Document ID.

When to use it
another tool knows the contract by its context, not by its Modusign ID.
Watch out
several documents can match, so pick a setting for multiple results.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into a find-or-create. Modusign exposes no find-or-create variant: its searches only look things up.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Modusign Zap breaks

Zapier ties no help article to Modusign, so the traps below are the general ones, read through a Zap that follows signatures.

Most come from how Zapier runs a Zap rather than from Modusign itself. If one of them is already biting, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap reacts only to what happens after you switch it on. Contracts signed earlier are never picked up, and moving that backlog is a separate job.

  • Four events, one trigger

    Document Updated reacts when a document is created, signed, completed or aborted. Check at the test what each run carries; a filter (paid plan) keeps only the event you need.

  • A Zap that sets itself off

    As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and eats tasks fast.

  • A sudden flood held back

    When a trigger returns a huge batch at once, after a bulk import or a migration, Zapier's flood protection can hold those runs back.
Need help

Need help automating Modusign with Zapier?

A person reads every message.

FAQ

Modusign Zapier integration: FAQ

01Is the Modusign Zapier integration free?
Yes, it works on the free plan, because Modusign is not a premium app. That plan gives you 100 tasks a month and as many Zaps as you want, but each Zap stops at two steps: one trigger and one action. A signed contract that adds a row to your spreadsheet fits. Add Get Document in between to fetch more details, or a filter, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a Modusign Zap use?
The trigger costs nothing: a document signed by everyone starts the Zap for free. After that, each action that succeeds counts as one task, and one that fails is not counted. So a Zap that goes from Document All Signed straight to a spreadsheet row uses one task per contract. With Document Updated, remember that the trigger covers four kinds of events, creation, signing, completion and abortion, and every run that reaches a successful action is billed.
03Is the Modusign integration real time?
Yes for both triggers. Document All Signed and Document Updated are instant: Modusign tells Zapier itself when the event happens, so the Zap starts right away, whatever your plan. The polling interval of the free plan does not apply to them, and the editor shows a lightning bolt on a Zap built on either one. What comes next, a search or an action, then runs in order inside that same Zap.
04What do you need to connect Modusign to Zapier?
An account on Modusign, plus read or write access on anything you do not own yourself and want the Zap to touch. In Zapier, open Apps, click + Add connection, search for Modusign, then click Add connection. A tab opens where you sign in to Modusign and grant Zapier access. If you plan to send documents, prepare a template in that same account first, since Request Document With Template needs a Template ID.
05Document Updated or Document All Signed: which one to pick?
It depends on what should set the Zap off. Document All Signed starts it once every signer has signed, which suits a Zap that only cares about closed contracts. Document Updated covers four moments in a document's life: creation, signing, completion and abortion. If you want its broader view but only one of those moments matters, add a filter right after it (paid plan), read at the test which value tells the events apart, and keep only the one you need.
06What if the Modusign operation you need isn't there?
Check the Modusign page on Zapier, which shows the list of operations currently on offer. Today that means two triggers, two actions and four searches. Template management, for instance, is not in it, so templates are prepared in Modusign itself. Before giving up, look at the searches: Get Document fetches the detailed properties of a document, and Search Documents finds one without its ID. The other two searches also start from a Document ID.
07Zapier, Make or n8n for Modusign?
Judge it on criteria, not on a ranking. Availability first: confirm that Modusign exists as a ready-made step in the other tool's own catalog, with the triggers you need. Then Zap length: on Zapier's free plan a Zap holds one trigger and one action, so the archive Zap with Get Document in the middle moves you to a paid plan. Then volume: every successful action is a task, and Document Updated covers four kinds of events, not just the final signature.
Same platform

Other docs you might need on this stack.

Browse all integrations