signNow Make integrationAutomate signNow with Make.

Pulls back a group invite so nobody can keep signing a package of documents that should no longer go out. The signers stop seeing a request that no longer makes sense.

Stops a pending signature request on one document, so the recipient cannot sign an outdated version by mistake. It keeps your pipeline clean when a contract has to be redone.

Writes your own entry into the signNow audit log, so the history of a document also shows what happened outside signNow. Auditors and colleagues see the full story in one place.

Makes a fresh copy of a template, ready to send, so every contract starts from the version your legal team approved. The template itself stays untouched.

Bundles several existing documents into one group, so the signer receives a single package instead of a string of separate requests. It suits onboarding packs and multi-part agreements.

Adds a new folder in signNow, which gives each client or project its own place before any document arrives. Your team stops hunting through one long list of files.

Produces a link to one document that you can share anywhere, on a website or in a chat, instead of sending an invite by email. According to signNow, people who receive the link can send invites to this document on your behalf.

Turns an existing document into a reusable template, which saves you from rebuilding the same fields every time. It is the bridge between a one-off contract and a repeatable one.

Removes a document from signNow for good, which keeps drafts and test copies from cluttering the account. Your folders then only show what people actually need.

Deletes a whole document group in one step, instead of taking a package apart by hand. It keeps the list of groups short and readable.

Removes a folder from the signNow account, the last step of a cleanup once a project is closed. The folder tree stays easy to browse for everyone.

Fetches the document file itself, as a PDF or a zip, so the next module can store it, attach it to an email or send it to accounting. This is how a contract leaves signNow.

Retrieves a file that a signer attached to the document, such as an ID scan or a proof of address, without opening signNow. The attachment becomes a file your scenario can pass along.

Reads the details of one document, so later modules can use its data rather than guessing. It answers the question of what a given document currently looks like.

Returns the documents inside a group along with their roles, which tells you who is expected to sign what. Handy before you send, resend or delete anything.

Shows where a group invite stands, with the status of each step and action, so you know exactly who has acted and who is holding things up. No more guessing from the inbox.

Creates a URL that downloads the document as a PDF, handy when the next tool wants a link rather than a file. The file itself never passes through your scenario.

Returns the details of the signNow user behind the connection, a quick way to confirm which account a scenario is really using. It removes doubt when several connections exist.

Calls any endpoint of the signNow API with the connection you already set up, which covers what the other modules do not. No separate authentication to manage.

Combines existing documents into one, so a signer or an auditor gets a single file instead of several. It fits when the parts of a deal were prepared separately.

Places a document in a chosen folder, so contracts land where your team expects them instead of piling up in one place. Filing becomes part of the flow.

Changes the name of a folder, which keeps the folder tree in line with the names used in your CRM or project tool. Colleagues find clients under the name they know.

Sends the invite emails for a group invite again, either to everyone still pending or to specific people. Reminders go out without you writing a single one.

Resends the invitation for a single document, a polite nudge that saves a manual follow-up. The signer simply receives the same request again.

Sends a document out for signature, either as a free-form invite or as a role-based invite. This is the module that turns a prepared file into an actual request in the signer's inbox.

Starts a multi-step invite on a document group, so several people sign one package in sequence. Each signer gets their turn without anyone passing the file along.

Sends a file from another app into signNow, so a document produced elsewhere can be signed there. It accepts .doc, .docx, .pdf, .xls, .xlsx, .ppt, .pptx and .png files.

Uploads a document that contains signNow text tags, so signature and date fields appear in place without manual setup. The tags written in the file do the layout work.

Returns the history of a document, one bundle per recorded entry, which gives you a trail you can store or report on. Useful when someone asks who did what and when.

Lists the documents inside one folder, so a scenario can work through a client's paperwork in one pass. Each document arrives as its own bundle.

Returns the folders sitting inside a given folder, which helps a scenario find its way through a nested structure. Think of it as opening one level of the tree.

Retrieves every folder of the connected user, which lets a scenario check whether a client folder already exists. That check stops duplicates before they happen.

Retrieves the documents of the connected user across the account, a starting point for bulk work such as exports or cleanups. It gives the whole picture, not one folder.

Returns the documents the user has modified, so a scenario can focus on what changed rather than everything in the account. Fewer bundles, fewer operations.

Retrieves all document groups of the account, each one as a bundle, so you can review or process packages in bulk. It is the overview behind any group-level report.

Returns the pending group invites of the user making the call, along with those already signed, which is the raw material for a reminder flow. If that user owns the document, fulfilled actions are included too.