Send NDAs From HubSpot Automatically

To send NDAs from HubSpot automatically, pick the deal stage where confidential material starts to flow, assign an NDA type and template to that pipeline, map deal, company and contact properties to the parties, check for an existing NDA before sending, and write the signing status back to the deal so reps never chase paper manually.

Most sales teams handle NDAs the same way. A prospect asks for a security review, a sandbox or a roadmap session, the rep realizes there is no agreement in place, and someone digs out last year's Word file, retypes the company name and emails a PDF. The deal waits. Automating the NDA from the CRM removes that wait, and it also removes the most common mistakes: the wrong template, the wrong legal name and a second NDA sent to a company that already signed one.

Why the deal stage is the right trigger

HubSpot organizes deals into pipelines, and each pipeline into deal stages. Stages describe where a deal is, which makes them a natural trigger for anything that should happen at a predictable point in the sale. NDAs fit that pattern well, because the need for one is tied to what you are about to share, not to a date on the calendar.

Triggering on a stage also means the NDA goes out when the deal is real. Sending one at first contact creates paperwork for prospects who never progress, and it can feel heavy-handed before anyone has shared anything sensitive. Sending one too late means the demo or the data room waits on signatures.

Which deal stage should send the NDA

Choose the first stage at which you share something you would not put on your website. For many B2B teams that is one of these:

• Technical evaluation, when solution engineers start walking through architecture, integrations or a sandbox.
• Security review, when the buyer sends a questionnaire and asks for policies, penetration test summaries or audit reports.
• Proposal or pricing, if your custom pricing and discount structure are sensitive.
• Partnership scoping, in a partner pipeline where both sides share roadmaps.

The goal is a signed NDA before the data-heavy demo, not after it. If your technical evaluation call is usually booked a week after the deal enters that stage, a stage trigger gives the prospect a week to sign, which is usually enough even when their legal team is involved.

Which NDA type to send

The type depends on who discloses. Getting this right avoids pushback from the prospect's legal team, who will ask why a one-sided agreement only protects you when they are also sharing their data.

When in doubt, a mutual NDA is the safer default for B2B sales, because it rarely triggers a negotiation. Our comparison of mutual and one-way NDAs covers the trade-offs in more detail.

Mapping HubSpot fields into the NDA

The NDA text should come from an approved template, not from free text in the CRM. Only party details and a few settings need to come from HubSpot. Everything else follows the clause library your legal team has already approved.

Two small changes in HubSpot make the mapping far more reliable. Add a company property for the legal entity name, and add a contact property or association label for the authorized signer. Without these, the NDA goes to whoever the rep talks to most, with whatever company name was typed when the record was created.

Avoiding duplicate NDAs

The same company can appear in several deals at once: a new business deal, an expansion deal, a partnership conversation. Without a check, each one sends its own NDA, and the prospect's legal team ends up reviewing three agreements on slightly different terms. Worse, nobody knows which one governs.

The fix is to check a register of signed NDAs before sending. A sensible rule looks like this:

1. Look up the counterparty in the NDA register by legal name.
2. If an NDA is signed, active and covers the right direction of disclosure, skip the send and record the existing agreement on the deal.
3. If an NDA was sent but not yet signed, skip the send and let reminders do their work.
4. If the last NDA has expired or ends within the next 30 days, send a new one.
5. If the existing NDA is one-way in the wrong direction, send a mutual NDA instead.

This only works if the register is complete, which is why signed NDAs should land there automatically. Good contract tracking software handles the lookup, the expiry dates and the reminders together.

Getting the status back to the deal

Reps should not need to leave HubSpot to know whether the paper is done. A deal property for NDA status, updated as the agreement moves through sent, viewed, signed or declined, lets you do useful things with standard HubSpot tools:

• Show NDA status on the deal record and in pipeline board views.
• Build a HubSpot workflow that creates a task for the rep when an NDA has been viewed but not signed after five days.
• Use the status as a requirement before a deal can move to the stage where the technical deep dive happens.
• Report on how long NDAs take to sign by pipeline or deal size.

The signed PDF itself is useful on the record too, especially for account managers who inherit the deal later.

Slack alerts for the deal team

Status on the deal record is good for reps who check HubSpot. For everyone else, a Slack message is faster. Useful alerts include an NDA signed (so the solution engineer can schedule the session), an NDA declined (so the rep can find out why), and an NDA expiring soon for an active customer. Keep alerts to the channel or person who acts on them, or people stop reading them.

How the HubSpot integration works in NonDisclosures

The HubSpot NDA integration is included in the Business and Company plans. An admin connects HubSpot once from the Integrations area of the workspace. You then choose a pipeline and the deal stage that should send an NDA, assign an NDA type and a team template to that pipeline, and map the HubSpot properties that hold the counterparty legal name, signer name, signer email and purpose.

When a deal enters the trigger stage, NonDisclosures checks its register for an active NDA with that counterparty. If one exists, the send is skipped and the existing agreement is recorded on the deal. If not, the NDA is generated from your template, with locked clauses staying locked, and sent for e-signature. The signer gets a personal link by email, valid for 30 days, and signs in the browser with a typed or drawn signature, without creating an account. The status is written back to a deal property you choose as the agreement moves through sent, viewed, partially signed, signed, declined, expired or voided, and unsigned signers get nudges.

Slack notifications for sent, viewed, signed, declined and expiring NDAs are also part of the Business plan. On the Company plan, the API and webhooks go further, for example using the nda.signed event to attach the signed PDF, with its certificate page and audit trail, to the HubSpot record, or to unlock a folder for the prospect.

NonDisclosures connects to HubSpot through HubSpot's standard authorization and APIs. It is not an official HubSpot product and does not claim a partnership, certification or marketplace listing from HubSpot. For the wider sales workflow, including what to share before and after signature, see our page on NDA for sales.

A rollout checklist

1. Agree the templates. Have legal approve one NDA type and template per pipeline, with protected clauses locked.
2. Clean the data. Add a legal name company property and a signer field, and fill them on open deals in the trigger stage and the stage after it.
3. Load the backlog. Upload existing signed NDAs to the register so the duplicate check sees them.
4. Test on one pipeline. Move a test deal with your own colleague as the signer, confirm the draft fills correctly and the status updates.
5. Tell the reps. Explain which stage sends the NDA, what they will see on the deal, and what to do if the prospect sends their own paper.
6. Turn on the alerts. Route signed and declined alerts to the people who act on them.

When the prospect sends their own NDA

Large buyers often insist on their own paper. In that case, pause the automatic send for that deal and review their draft instead. Upload it to NonDisclosures and run AI contract review to get a plain-language summary, a risk score and flagged clauses with suggested fallbacks, then store the signed version in the same register so the duplicate check knows it exists.

Want to see the agreement your pipeline would send? Generate an NDA preview without an account, pick mutual or one-way, the term and governing law, and see the document before you connect HubSpot.

This article is general information about US practice, not legal advice. NonDisclosures is a software tool, not a law firm. Laws differ by state, so have a licensed attorney review agreements that matter.