Ops · n8n

Auto-Send an NDA for E-Signature When a New Client Is Added

An n8n workflow that fires when a new client is created in your CRM, sends them your NDA through an e-signature provider, and updates the record when it's signed — so paperwork happens the moment a relationship starts instead of days into the project.

difficulty Intermediatesetup 50 minresult Every new client is sent an NDA to e-sign automatically, and the CRM reflects the signed status
  1. 1

    Trigger on new client

    A Webhook catches the CRM 'new client' event with name, email and record ID.

  2. 2

    Send the NDA

    An HTTP Request calls your e-signature provider to create a signature request from your NDA template, pre-filling the client's name and email.

  3. 3

    Listen for completion

    A second Webhook receives the provider's completed event when the client signs the document.

  4. 4

    Update and notify

    An HTTP Request marks the CRM record's NDA field as signed, and a Slack node tells the account owner they're cleared to proceed.

Frequently asked questions

Which e-signature tools work?

Any with an API — DocuSign, Dropbox Sign, PandaDoc, SignWell. The workflow sends a signature request from your NDA template with the client's name and email pre-filled, then listens for the 'completed' webhook to mark it done.

How does it know when the NDA is signed?

A second webhook receives the provider's 'document completed' event. That updates the CRM record's NDA field to signed and can notify the account owner — closing the loop without anyone checking the signing dashboard.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.