Resources · Zapier integration

neosigna Zapier integrationAutomate neosigna with Zapier.

neosigna Zapier integration: 1 trigger, 5 actions, 3 searches. The contract management platform can start a Zap when a contract is created, receive new contracts, counterparties, drafts and users, and let a Zap find a contract, its latest version or one component.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the neosigna Zapier integration is good for

The neosigna Zapier integration links the collaborative contract platform to the other tools around it. A Zap, the automation you build on Zapier, can start when a contract is created in neosigna, or write into neosigna from another app: a counterparty, a contract, a new draft, a user, or the value of one component.

Three results worth building. A contract register outside neosigna: New Contract Created adds each new contract to a spreadsheet or a team channel. Counterparties that arrive ready: Create Counterparty records a company or an individual coming from another tool, so contracts can be built on it. A field kept in sync: Get Contract finds the contract from its code, Get Latest Version of Contract returns its draft or live version, Get Component picks the right component, and Update Component changes its value.

What Zapier does not do here matters too. The only trigger is polling, so it waits for Zapier's next check, and it only sees new contracts, not changes or signatures. There is no delete action. And Create Contract needs four internal IDs (type, counterparty, legal entity, owner) that no neosigna search returns; only the counterparty can be created in the same Zap, with Create Counterparty, and whether its result carries the ID is something to check at the test. For a wider view on the tool, read our Zapier review or the Make vs Zapier comparison.

Vocabulary

Zapier terms, in plain words

Eight terms come back on this page. Each one is explained once here, then used without repeating.

Zap
The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. In neosigna there is just one: a new contract being created in the account.
Action
What the Zap does once started, such as creating a counterparty or updating a component value.
Task
The unit Zapier bills: one action completed successfully. Your monthly quota is a count of those.
Polling trigger
A trigger Zapier checks on a timer, keeping only what it has not seen before. The neosigna trigger works this way.
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 that already exists, such as a contract or a component, for the next steps to use.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter, a search or a second action makes one, and it needs a paid plan.
Cost

What a neosigna Zap costs

neosigna is not a premium app, so it works on the free plan. Zapier bills tasks, and a task is a completed action, nothing more.

  • Free plan100 tasks per month, two-step Zaps
  • Premium appNo
  • Trigger typePolling, 1 of 1

Watching neosigna for new contracts is free, however often Zapier checks, and the trigger never costs a task. Each create or update that succeeds counts once; a failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps of two steps. That limit bites here: Update Component needs a component ID, which comes from Get Component, and a search makes the Zap multi-step, so paid. The neosigna trigger is a polling one, so the grid below sets how long a new contract can wait before the Zap sees it.

Connect

Connect neosigna to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your neosigna account linked to Zapier once, then reused by every neosigna step.

  2. 02

    Pick neosigna and sign in

    Search neosigna in the dialog, select it and click Add connection. Sign in to neosigna in the tab that opens, with the account whose contracts the Zap should read or write.

  3. 03

    Grant access

    Let Zapier into the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. Each neosigna step then reuses this connection.

First Zap

Your first Zap: post selected new contracts to your team chat

GoalWhen a contract is created in neosigna, a filter keeps only the ones you care about, and a message goes to your team chat.

  1. 01

    Set the trigger

    Create a Zap, choose neosigna and New Contract Created, then your connection. Test it: Zapier brings back the three most recent contracts so you map a real one.

  2. 02

    Add a filter

    From the plus icon, add Filter and fill the three boxes: the contract field to look at, the rule, and the value to compare with. A filter makes the Zap multi-step, so this version needs a paid plan.

  3. 03

    Add the message

    Add your team chat app and its send action. Build the message from contract fields returned by the trigger, so readers know which contract appeared without opening neosigna.

  4. 04

    Test each step

    Run each step once and read what came back before going further. Check what the filter decided about the test contract, then the message that was actually posted.

  5. 05

    Publish

    Click Publish to switch the Zap on. Contracts created from then on, and passing the filter, post a message; older contracts stay out of it.

Triggers

neosigna trigger

1 event starts a Zap when something happens in neosigna. Zapier checks for them at the interval your plan allows.

1

New Contract Created

Polling trigger

In Zapier“Triggers when a new contract is created.”

Starts your Zap each time a contract is created in neosigna and hands its details to the next step. It is the only trigger the app offers on Zapier, so every flow that reacts to neosigna begins here, whether it feeds a register, a team message or a task list.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
each new contract should show up in a spreadsheet or a channel your team already reads.
Watch out
it reacts to creation only; a contract that changes version or gets signed does not start the Zap.
Actions

neosigna actions

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

1

Create Contract

Action

In Zapier“Creates a new Contract (and its Draft version).”

Creates a new contract in neosigna, together with its draft version.

When to use it
a contract request recorded in another tool should open the matching contract without retyping.
Watch out
four internal IDs are mandatory, for the contract type, the counterparty, the legal entity and the owner. Of the four, only the counterparty can be created by another neosigna step, Create Counterparty; check at the test what ID it returns.
2

Create Counterparty

Action

In Zapier“Creates a new counterparty.”

Records a new counterparty in neosigna, either a company or an individual.

When to use it
a counterparty captured in another tool should be ready in neosigna before any contract is built.
Watch out
the kind is typed as a number, 0 for a company and 1 for an individual, and both the counterparty name and the legal name are mandatory.
3

Create Draft

Action

In Zapier“Creates a new Draft version for a Live Contract.”

Opens a new draft version of a contract that is already live, so changes can start from there.

When to use it
a change requested elsewhere should open a fresh draft in neosigna.
Watch out
it needs a version ID; Get Latest Version of Contract can supply it after Get Contract.
4

Create User

Action

In Zapier“Creates a new user and automatically invite him/her to setup his/her account.”

Adds a user to neosigna, and the app invites that person to set up their account.

When to use it
a newcomer listed in another tool should get neosigna access without someone creating it by hand.
Watch out
first name, last name, email and a role ID are all mandatory, so know the ID of the role you want to give.
5

Update Component

Action

In Zapier“Update the value of a component based on its internal id.”

Changes the value of one component of a contract, targeted by its internal ID.

When to use it
a value agreed in another tool should be written into the contract without opening it.
Watch out
the component ID is mandatory, and Get Component can return it, provided you give it a version ID.
Searches

neosigna searches

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

A search step finds something that already exists and hands it to the following steps. In neosigna the three searches chain: contract, then latest version, then component. They sit at the bottom of the action-event list, under SEARCH, and a Zap with one is multi-step, so paid. Three settings decide what happens when the result is not clean.

1

Get Component

Search

In Zapier“Get a component (including its internal id) from a given Contract version, based on a Component code.”

Fetches one component of a contract version from its code, and returns its internal ID with it.

When to use it
right before Update Component, to target the right field of the right version.
Watch out
both the version ID and the component code are mandatory, so Get Latest Version of Contract can sit just before it to supply the version.
2

Get Contract

Search

In Zapier“Returns a Contract matching a Contract Code.”

Returns the contract that matches a contract code, the code you can read in neosigna itself.

When to use it
another tool carries the contract code and the Zap needs the contract's internal ID.
Watch out
the code is mandatory; copy the exact form shown in neosigna and test with a real one.
3

Get Latest Version of Contract

Search

In Zapier“Get the latest version of a Contract based on a Contract internal id. Draft if it exists, Live otherwise.”

Brings back the most recent version of a contract from its internal ID: the draft if one exists, the live version otherwise.

When to use it
after Get Contract, to get the version ID that Get Component and Create Draft need; check at the test that Get Contract does return the contract's internal ID.
Watch out
the result can be a draft or a live version depending on the contract; check which one the test returns.

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. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. neosigna exposes no find-or-create entry in the editor, so none of its searches offers it.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on.
When it breaks

When a neosigna Zap breaks

Zapier attaches no help article to neosigna, so these cases are the general limits of any Zap, read for a contract platform.

Each has a plain cause and a plain fix. If a Zap still misbehaves after these checks, our Zapier troubleshooting page is the next stop.

  • Existing contracts never come through

    A Zap only reacts to what happens after you switch it on. Contracts created before publishing are not picked up; moving that history is a separate job.

  • A Zap that keeps restarting

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

  • A bulk import gets held back

    When the trigger suddenly returns a huge batch, after a bulk import or a migration of contracts, Zapier's flood protection can hold those items back.

  • Each contract runs once

    On a polling trigger, Zapier keeps track of what it has already seen, so the same contract does not start the Zap twice.
Need help

Need help automating neosigna with Zapier?

A person reads every message.

FAQ

neosigna Zapier integration: frequent questions

01Is the neosigna Zapier integration free?
Yes, for Zaps of two steps. neosigna is not a premium app, so its trigger plus one action, or another app's trigger plus one neosigna action, runs on the free plan. That plan gives 100 tasks a month and an unlimited number of Zaps. The three searches change things: any Zap with a search is multi-step and needs a paid plan or the free trial, and updating a component depends on Get Component. A filter or a second action has the same effect.
02How many tasks does a neosigna Zap use?
One task per action that succeeds. The trigger costs nothing, and Zapier checking neosigna for new contracts costs nothing either, however often it looks. Creating a counterparty, a contract, a draft or a user, or updating a component, counts once when it works; a failed action is not counted. A Zap that creates a counterparty and then a contract for it uses two tasks per run. With 100 tasks on the free plan, count what your Zaps will write, not what they watch.
03Is neosigna real-time on Zapier?
No. New Contract Created is a polling trigger: Zapier goes and checks neosigna for new contracts at a fixed interval set by your plan. That is every 15 minutes on Free, 2 minutes on Professional, and 1 minute on Team and Enterprise. On paid plans the interval can be changed, and a check can be run by hand from the editor. As the app has no instant trigger, no plan makes the Zap start without waiting for the next check.
04What does connecting neosigna to Zapier require?
An account on neosigna, plus read or write access on anything you do not own yourself and want the Zap to touch. From the Apps page of Zapier, click + Add connection, search neosigna, click Add connection, sign in to neosigna in the tab that opens and grant access. The connection is made once and reused by every neosigna step. Create Contract then asks for four internal IDs: contract type, counterparty, legal entity and owner.
05Why is Create Contract so strict about IDs?
Because a neosigna contract hangs on four internal IDs, all mandatory: the contract type, the counterparty, the legal entity and the owner. None of the three searches on Zapier returns a type, a legal entity or an owner, so those IDs have to be known up front. The counterparty is different: Create Counterparty can create it earlier in the same Zap, and the test shows whether its result carries the ID. Two actions make the Zap multi-step, so that version needs a paid plan. Check the contract created at the test step before publishing.
06What if the neosigna operation you need is missing?
Then Zapier does not offer it today, and no setting will reveal it. The neosigna page on Zapier shows the current list of operations, so check it before you build. Some gaps are visible already: a single trigger, on new contracts only, nothing on signatures or version changes, and no delete action. Design the Zap around the nine operations that page lists, and confirm at the test step that each one returns what the next step needs before you publish.
07Zapier, Make or n8n for neosigna?
Decide on criteria, not on a ranking. First, availability: on Zapier, neosigna offers 1 trigger, 5 actions and 3 searches; check whether Make and n8n list the app in their own catalogs. Second, flow length: changing a component means chaining searches before the update, which already means a paid Zapier plan. Third, timing: the only trigger is polling, so the plan interval sets the wait. Fourth, how each tool counts usage; Zapier only bills completed actions.
Same platform

Other docs you might need on this stack.

Browse all integrations