Resources · Zapier integration

Legalesign Zapier integrationAutomate Legalesign with Zapier.

The Legalesign Zapier integration gives you 3 triggers, 2 actions and 2 searches. Zaps can react when a document is sent, signed or rejected, send a signature request for you, and fetch signed files or fields. Every trigger is instant.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Legalesign Zapier integration does for you

Legalesign is electronic signature software: you send documents out, people sign or reject them, and you keep the signed files. Zapier connects apps so that an event in one starts work in another. With Legalesign, three signing events can start a Zap, and four operations let a Zap send or fetch things.

Three results show up most often. A signed-contracts log: with New Signature Request Signed, each completed signature adds a line to a spreadsheet, so you never ask around to know what is done. A signature request sent from elsewhere: with Create a PDF Document Signature Request for a Single Signer, a deal closed in your CRM can send the matching template to the right person on its own. A signed file put where it belongs: with Create Download Document Url, a Zap gets a link to the signed document and can hand it to the next step.

The two searches, Signer Fields and Template Sender Fields, read what was filled in on a completed document or what a template expects from the sender.

Now what Zapier does not do here. The signature request action handles one signer per document, not several. There is no action to cancel or resend a request. And nothing that happened before the Zap was published is sent. If you are comparing platforms, the Make vs Zapier comparison and the Zapier training are the next pages to open.

Vocabulary

Zapier vocabulary for a Legalesign Zap

Seven terms are enough for the rest of this page. Each is explained once here, then used as is.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts a Zap. Once the Zap is on, Zapier waits for it. Legalesign has three: sent, signed, rejected.
Action
What the Zap does once it starts: the step that writes, sends or moves something for you, like a signature request.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts these.
Instant vs polling
An instant trigger is pushed by the app the moment it happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What Legalesign Zaps really cost

Legalesign is not a premium app, so it runs on the free plan. Its three triggers are instant, so the check intervals that slow down polling apps never apply to them.

  • TriggersFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Search or filterMakes the Zap multi-step, paid plan

A trigger never costs a task: a document sent, signed or rejected reaching Zapier is free. Each action that succeeds counts once, and a failed one is not counted. Sending one signature request is one task. The free plan gives you 100 tasks a month and Zaps of two steps only. That is the catch with Legalesign: adding a search step before an action, or a filter, or a second action, makes the Zap multi-step, and a multi-step Zap needs a paid plan. The interval grid below does not apply to Legalesign, since all its triggers are instant.

Connect

Connect Legalesign to Zapier in three steps

  1. 01

    Open Apps

    In your Zapier account, go to Apps and click + Add connection. A connection is your Legalesign account linked to Zapier once, then reused by every Zap that needs it.

  2. 02

    Choose Legalesign

    Search for Legalesign in the dialog, select it and click Add connection. A new tab opens on the Legalesign side, where you sign in with your usual login.

  3. 03

    Sign in and grant access

    Log in to Legalesign and allow Zapier in. You need your own account, plus access to the groups, templates and documents you do not own but want the Zap to use.

First Zap

Your first Zap: log every signed document

GoalEach time a document is signed in Legalesign, add a line to a spreadsheet so the team has one list of everything signed.

  1. 01

    Pick the trigger

    Create a Zap, choose Legalesign as the app that starts it and New Signature Request Signed as the event, then select your connection.

  2. 02

    Test on a real signature

    Run the trigger test. Zapier brings back the three most recent signed documents of the account, so you map the next step on a real one.

  3. 03

    Add the spreadsheet step

    Add the action in your spreadsheet app and map the document details into the columns you want. Two steps in total keeps the Zap on the free plan.

  4. 04

    Check the row

    Test the action and open the sheet: the new row should be there. If a column is empty, adjust the mapping and test again before going on.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, each signature adds its line the moment Legalesign reports it, with nobody typing it in.

Triggers

The three Legalesign triggers

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

1

New Signature Request Rejected

Instant trigger

In Zapier“Triggers when a new document has been Rejected.”

Fires when someone rejects a document you sent through Legalesign, and passes that document to the next steps. A rejection usually needs a quick reaction, which is what this trigger is for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the person who sent the document should hear about the refusal at once, by message or email.
Watch out
rejections that happened before the Zap was published are never sent.
2

New Signature Request Sent

Instant trigger

In Zapier“Triggers when a new document has been Sent.”

Starts your Zap each time a document goes out for signature. It marks the beginning of the signing journey, so it suits anything that tracks what is pending.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when each sent document should open a follow-up task or update a deal in your CRM.
Watch out
a Zap that sends a signature request through the action can set this trigger off again, so avoid pairing them in a loop.
3

New Signature Request Signed

Instant trigger

In Zapier“Triggers when a new document has been Signed.”

Runs when a document has been signed, and hands it to the steps that follow. This is the event most teams wait for, since it closes the loop.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a signature should update a register, tell the team, or start the retrieval of the signed file.
Watch out
Create Download Document Url only returns a link; storing the file somewhere takes one more action, which makes the Zap multi-step.
Actions

The two Legalesign actions

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

1

Create a PDF Document Signature Request for a Single Signer

Action

In Zapier“Creates and sends a new PDF Document Signature Request to a single signer.”

Creates a signature request from one of your templates and sends it to one signer, with their first name, last name and email.

When to use it
when a deal closed or a form filled in another app should trigger the contract automatically.
Watch out
Group Name, Document Name, Template ID, Firstname, Lastname and Email are all required, and the signer email is only sent if you switch it on.
2

Create Download Document Url

Action

In Zapier“Returns a document url.”

Returns a link to a signed document, which later steps can use to store or share the file.

When to use it
right after a signature, to pass the signed file to another app or attach it to a record.
Watch out
it needs the Signed Document ID, so an earlier step must provide that identifier.
Searches

The two Legalesign searches

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

A search step looks up something that already exists, here in Legalesign, and hands what it found to the steps after it. Searches sit at the bottom of the action-event list, under SEARCH. Three settings decide what happens when the result is not the expected one.

1

Signer Fields

Search

In Zapier“Return any Signer fields from a completed document.”

Reads the fields a signer filled in on a completed document, so the values can travel to another app.

When to use it
after a signature, to copy what the signer entered into your CRM or a spreadsheet.
Watch out
it only works on completed documents, and adding it makes the Zap multi-step.
2

Template Sender Fields

Search

In Zapier“Find the templates sender fields.”

Finds the sender fields a template expects, so you know what to fill before sending a request.

When to use it
before the signature request action, when your template has sender fields to complete.
Watch out
the Template ID is required, so copy it from Legalesign before you set the step up.

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 relied on it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Neither Legalesign search offers that variant, so you will not see it here.
  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 pass all of them on at once.
When it breaks

When a Legalesign Zap breaks

Zapier links no help article and no rate limit specific to Legalesign. Most failures come from required fields or from the way Zapier works.

Six cases cover most surprises. If a Zap still misbehaves after that, the Zapier troubleshooting guide is the next page to open.

  • Past signatures never arrive

    A Zap only reacts to what happens after it is switched on. Documents sent, signed or rejected before that stay in Legalesign, and moving them is a separate job.

  • The signature request stops

    Group Name, Document Name, Template ID, Firstname, Lastname and Email are all required. One empty value and the request is not sent.

  • The signer never got an email

    Send an email defaults to false. Leave it off and the request is created without the signer being emailed by it.

  • No link without an ID

    Create Download Document Url needs a Signed Document ID. If the earlier step does not pass one, the action has nothing to fetch.

  • A search that stops the Zap

    By default, a search that finds nothing ends the Zap there. Switch on Successful if no search results are found? if the next steps can run without it.

  • A sending loop

    A Zap on New Signature Request Sent that also sends a request writes where its own trigger watches, and can set itself off again and again.
Need help

Need help automating Legalesign with Zapier?

A person reads every message.

FAQ

Legalesign Zapier integration: frequent questions

01Is the Legalesign Zapier integration free?
Yes. Legalesign is not a premium app, so its triggers, actions and searches work on Zapier's free plan. That plan covers 100 tasks a month and Zaps of two steps, one trigger and one action. A Zap that logs each signed document in a spreadsheet fits inside it. As soon as you add a search, a filter or a second action, the Zap becomes multi-step and needs a paid plan. Zapier's prices change often, so check its pricing page before planning a budget.
02How many tasks does a Legalesign Zap use?
One task per action that succeeds, and none for the trigger. A document sent, signed or rejected reaching Zapier costs nothing. If the Zap then adds a row, that is one task. If it fetches a download link and stores the file, that is two per signed document. Sending a signature request through Legalesign also counts as one task. An action that fails is not counted against your plan, though it is worth checking so no contract goes missing.
03Do Legalesign triggers work in real time?
Yes. All three Legalesign triggers are instant: Legalesign tells Zapier the moment a document is sent, signed or rejected, and the Zap starts right away. That is true on every plan, the free one included, so the check intervals of the plans do not apply. In the editor, an instant trigger shows a lightning bolt. Whether a trigger is instant is decided by the app, and it cannot be switched from Zapier.
04What is needed to connect Legalesign to Zapier?
A Legalesign account, plus access to the groups, templates and documents the Zap will use. In Zapier, open Apps, click + Add connection, search for Legalesign and click Add connection. A tab opens where you sign in and grant Zapier access. The connection is saved and reused by every Legalesign Zap. Before you use the signature request action, have a template ready and know its group, since both are required on every run.
05Why did the signer not receive the signature request?
Most likely because the Send an email option was left on its default, which is false. With it off, the action creates the request without emailing the signer. Switch it on in the action if you want Legalesign to send the email. Also check that the Email field received a real address from the earlier step, since it is required. If any required field is empty, the request is not created at all, and the Zap history will show the failed run.
06What if the Legalesign operation you need is not available?
Then this integration does not offer it today. On Zapier, Legalesign has three triggers, two actions and two searches. The signature request action handles a single signer, and there is no action to cancel or resend a request. Anything built from sent, signed and rejected events, single-signer requests, download links and field lookups is covered. For the rest, the answer sits outside this integration, for instance in another automation tool, which is worth checking first.
07Zapier, Make or n8n for Legalesign?
It depends on your criteria rather than on a ranking. On Zapier, Legalesign comes with three instant triggers, two actions and two searches ready to use, and the setup is short, which suits a team that wants signatures flowing into its other tools quickly. For any alternative, check whether it has a Legalesign connector, whether it covers several signers, and how it bills each run. Then weigh your budget, the steps per flow and who will maintain it.
Same platform

Other docs you might need on this stack.

Browse all integrations