D4Sign Zapier integrationAutomate D4Sign with Zapier.
D4Sign Zapier integration: 8 triggers that Zapier checks on a timer, 10 actions to upload, send, cancel and file your contracts, and 0 searches. What each operation does, what a run costs and what breaks, before you open the editor.
Verified Trustpilot reviews · AI, automation & growth agency
What the D4Sign Zapier integration does for your contracts
The D4Sign Zapier integration links your D4Sign e-signature account to Zapier. New documents, safes, folders or templates found in D4Sign can start work, and other tools can tell D4Sign to upload a file, add signers, send a document for signature or cancel it. You set it up once, it runs hands-off.
Offer letters out the door. HR drops a new offer letter into D4Sign. List Documents picks it up, Create Document Signers List adds the person who signs for the company and Send Document to Signer sends it with your message. Nobody chases the file around.
Contracts from a template. Create Document From Template produces a new document from one of your D4Sign templates, named the way you decide, inside the safe you pick. The standard contract stops being copied by hand.
A tidy account. Create Folder and Rename Folder keep safes organized, and Cancel Document withdraws a document with a comment that explains why.
What Zapier does not do here: none of the eight triggers is instant. Zapier checks D4Sign on a timer, every 15 minutes on the free plan, so a new document never starts a Zap the second it appears. There is no search step either, which means you cannot look up a document by name before acting on it. Several actions ask for a document UUID, so that value has to come from an earlier step. And a Zap only sees what is new after you switch it on: documents already in your account are not processed.
Looking at other tools? The D4Sign Make integration has its own page, and Make vs Zapier puts both platforms side by side.
Zapier words you need for this page
Six terms come back all through this page. Here they are once, in plain English.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it and does nothing else until it shows up.
- Action
- What the Zap does once it has started: the step that uploads, sends, creates or cancels something for you.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant trigger
- A polling trigger is checked by Zapier on a timer and keeps only what is new. An instant one is pushed by the app. D4Sign only has polling triggers.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly otherwise.
What a D4Sign Zap costs you
Zapier bills the actions that work. The trigger is free, and so is every check Zapier runs on D4Sign, however often it happens.
- Trigger and checksFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Filter or second actionMakes the Zap multi-step, paid plan
- Premium appNo, D4Sign runs on the free plan
Each successful action is one task: a three-action Zap costs three times what a one-action Zap costs. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. D4Sign is not a premium app, so it works on the free plan. Since all its triggers are polling ones, the interval grid below applies to every one of them.
Connect D4Sign to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your D4Sign account linked to Zapier once, then reused by every step that works with D4Sign.
- 02
Pick D4Sign
Search for D4Sign by name in the dialog, select it, then click Add connection. You need an existing D4Sign account, plus access to the safes and documents you want the Zap to read or change.
- 03
Sign in and grant access
Sign in to D4Sign in the tab that opens and grant Zapier access to the account. Every Zap you build afterwards can pick this connection without asking for your credentials again.
Your first D4Sign Zap: offer letters sent for signature
GoalWhen HR adds an offer letter to D4Sign, keep only the documents this Zap is meant for, add the HR manager who signs them and send the letter for signature.
- 01
Build: pick the trigger
Start a new Zap, choose D4Sign, then List Documents. Select your D4Sign connection. Zapier will check for new documents on your plan's interval.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of your account, so you map the next steps on a real document and not on a guess.
- 03
Add the filter
From the plus icon, add Filter. Pick, among the fields the test brought back, the one that tells offer letters apart, then the rule and the value to compare with. A text rule only works on text.
- 04
Add the signer
Choose Create Document Signers List. Both fields are required. Check that the document's UUID is among the values the trigger test showed and map it, then type the HR manager's email: the same signer every time.
- 05
Send, test, Publish
Add Send Document to Signer with your message and the workflow option, test each step, then click Publish. With a filter, this Zap needs a paid plan.
D4Sign triggers: 8 polling events
8 events start a Zap when something happens in D4Sign. Zapier checks for them at the interval your plan allows.
List Documents
Polling triggerIn Zapier“Triggers when documents are found.”
Starts your Zap when Zapier finds a document it has not seen before in your D4Sign account. It is the broadest entry point of the integration: any new contract, letter or form can kick off the follow-up.
List Signing Groups
Polling triggerIn Zapier“Triggers when listing all groups of a safe.”
Watches the signing groups of one safe and starts the Zap when a new group shows up there. Useful when groups mirror teams or approval chains that other tools need to know about.
List All Safes
Polling triggerIn Zapier“Triggers when a new safe is found.”
Fires when Zapier finds a new safe in your D4Sign account. Safes are the top level where documents live, so a new one usually means a new client, department or project.
Get Document by UUID
Polling triggerIn Zapier“Triggers when Retrieves the details of a specific document by its UUID.”
Brings back the details of one specific document, the one whose UUID you enter. Since Zapier never starts a Zap twice for an item it has already seen, it gives you that document once; it does not report its later changes.
List Document Webhooks
Polling triggerIn Zapier“Triggers when lists all webhooks configured for a document.”
Lists the notification addresses set on one document, the places D4Sign reports to about it. It belongs to the technical side of the integration and mostly serves whoever maintains those links.
List Folders
Polling triggerIn Zapier“Triggers when Lists folders from a Safe.”
Watches the folders inside one safe and starts the Zap when a new folder appears. Handy when folders stand for deals, hires or projects.
List Document Signers
Polling triggerIn Zapier“Triggers when returns document information and all signatories linked to it.”
Returns the information of one document along with every signer linked to it. It answers a precise question: who is on this document right now.
List Templates
Polling triggerIn Zapier“Triggers when list a templates found.”
Starts the Zap when Zapier finds a template it has not seen before in your account. It keeps the people who write contracts in step with the people who use them.
D4Sign actions: what your Zap can do
D4Sign gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Cancel Document
ActionIn Zapier“Cancels an existing document by sending a cancellation comment.”
Cancels an existing document and records a comment explaining why. It closes the loop when a deal falls through.
Create Document Signers List
ActionIn Zapier“Adds or creates the list of signers for a document.”
Adds signers to a document or creates its signer list. It prepares the document before you send it.
Create Document From Template
ActionIn Zapier“Creates documents from a template model.”
Generates a new document from one of your D4Sign templates. You choose the safe, the template type, the template and the new document's name.
Create Document Webhook
ActionIn Zapier“Creates a webhook for a document.”
Registers a webhook on a document: an address that will receive that document's events. This one is for teams with a developer or a receiving tool ready.
Create Folder
ActionIn Zapier“Creates a new folder inside a safe.”
Adds a folder inside a safe, with the name you give it. Good for keeping one folder per client, hire or project.
Get Account Balance
ActionIn Zapier“Retrieves the account balance.”
Retrieves your D4Sign account balance so the next steps can use it. It writes nothing, it reads.
Remove Document Signer
ActionIn Zapier“Removes a signer from a document using the signer email and key.”
Takes a signer off a document, using their email and signer key. It fixes a wrong recipient without starting over.
Rename Folder
ActionIn Zapier“Renames an existing folder inside a safe.”
Changes the name of an existing folder inside a safe. Useful when a project, client or status changes and the folder should say so.
Send Document to Signer
ActionIn Zapier“Sends an existing document for signing.”
Sends an existing document out for signature, with a message to the signers. It is the step that actually starts the signing.
Upload Document
ActionIn Zapier“Uploads a new document.”
Puts a new file into D4Sign, in the safe and folder you choose. It is the starting point when the contract is produced in another tool.
When a D4Sign Zap breaks
Zapier attaches no help article to D4Sign, and no D4Sign-specific limit is documented. What goes wrong comes from how Zaps work in general.
Four cases come back on document automations. None of them is a bug: each one follows from how Zapier checks and remembers what it has seen. When one hits you, the Zapier troubleshooting page is the next stop.
Documents already in D4Sign are skipped
A Zap only reacts to what is new after you switch it on. Contracts already in your account never start it; moving that backlog is a separate job.The Zap that feeds itself
A Zap on List Documents that runs Upload Document or Create Document From Template creates a new document, which the trigger then finds. It loops and burns tasks fast.A bulk import floods the trigger
Uploading a large batch of contracts at once can make the trigger return a huge set, and Zapier's flood protection can hold it back.Not instant, by design
Zapier checks D4Sign on a timer and remembers what it has seen, so a document never starts the Zap twice, but it also never starts it before the next check.
Need help automating D4Sign with Zapier?
A person reads every message.



