N8N Contract and Proposal Automation: From CRM to Signed Deal Automatically

Every sales rep knows the feeling: a discovery call ends on a high note, the prospect says "send me something," and then two days pass before the proposal arrives. By then, a competitor has already followed up twice and the prospect has started a trial somewhere else.

The delay is rarely laziness. It is process friction. Someone has to pull deal details from the CRM, populate a Word doc or Canva template, export a PDF, write a custom email, attach the file, and send it. Then remember to follow up three days later when the prospect goes quiet. Then again at seven days. Then update the CRM stage. For every deal.

N8N can handle all of that. Not with some generic "AI will figure it out" handwave, but with a specific, reproducible workflow that triggers on a CRM stage change and runs through to a signed contract landing in your inbox. This guide shows you exactly how to build it.

What This Workflow Actually Does

Before getting into the nodes, here is the full flow so you can see what you are building:

1. Trigger: A deal moves to your "Proposal" stage in HubSpot or Pipedrive
2. Data pull: N8N fetches the deal's contact, company, service scope, and pricing from the CRM
3. Document creation: N8N calls PandaDoc or DocuSign to create a pre-filled proposal from a master template
4. Send: The e-signature platform emails the proposal to the prospect automatically
5. Follow-up sequence: If the proposal is viewed but not signed within 48 hours, N8N sends a follow-up email from your sales rep's inbox
6. Signed: When the prospect signs, N8N updates the CRM stage, notifies your team on Slack, and triggers your client onboarding workflow
7. Archive: The signed PDF is saved to Google Drive in the client's folder and linked back to the CRM deal

That entire sequence runs without a human touching it. The sales rep's only job is to move the deal to the Proposal stage after the call. Everything after that is automated.

Why Proposal Speed Matters More Than You Think

Research from the B2B sales world consistently shows that proposals sent within one hour of a sales call close at significantly higher rates than those sent the next day. The prospect is most excited immediately after the conversation. Every hour that passes is friction, dilution of momentum, and an opening for a competitor.

For SMBs where one salesperson is handling five to fifteen active deals simultaneously, manual proposal creation creates a bottleneck that compounds. The salesperson cannot send proposals fast because they are busy with other calls. They cannot do the follow-up consistently because there are too many deals to track. The CRM data stays stale because updating it takes time. N8N solves all three problems in a single workflow.

At Le Marquier, we used AI automation to reduce the operational overhead in their customer engagement workflow by 80% and achieve a 98% handling rate on automated sequences. The principle applies directly to proposal workflows: automate the mechanical steps so your team focuses on the conversations that actually close deals.

Tool Stack for This Workflow

You will need at least one tool from each category:

• Automation platform: N8N (self-hosted or cloud)
• CRM: HubSpot, Pipedrive, or any CRM with a webhook or API
• E-signature and proposals: PandaDoc (easier API, template system) or DocuSign (more enterprise, more setup)
• Email: Gmail or your SMTP provider for follow-up sequences
• Notifications: Slack
• Storage: Google Drive or Dropbox for signed contract archival

PandaDoc is the recommended choice if you are starting from scratch. Their API lets you create a document from a template, prefill variables, add recipients, and send for signature in a single API call. DocuSign requires more calls and more credential setup, but it is the right choice if your clients expect or require it.

Building the Workflow: Step by Step

Step 1: The CRM Trigger

In N8N, add a HubSpot Trigger node (or Pipedrive Trigger if you use Pipedrive). Configure it to listen for deal stage changes. You want to fire specifically when the deal stage becomes your "Proposal Sent" or "Proposal Ready" stage, not on every deal update.

If your CRM does not have a native N8N trigger node, use the Webhook node instead. Most CRMs let you configure a webhook URL to call when specific events occur. Paste the N8N webhook URL into your CRM's automation settings and you get the same result.

Step 2: Pull Full Deal Data

The trigger fires with some deal data, but you almost always need more. Add an HTTP Request node (or the native HubSpot node) to fetch the full deal object including associated contacts and companies. This gives you every field you need: contact name, email, company, deal value, service tier, start date, and any custom fields your team uses.

Use a Set node to extract and rename the fields you will pass to the proposal template. Clean field names at this step make the rest of the workflow readable. For example, map properties.firstname to contactFirstName and dealname to projectTitle.

Step 3: Create the Proposal Document

Add an HTTP Request node to call the PandaDoc API. The key endpoint is POST /documents. In the request body, specify your template ID and pass the mapped variables from Step 2 as the tokens array. PandaDoc will substitute these into the template placeholders automatically.

The API response includes a document ID. Store this in a Set node for use in later steps. You will need the document ID to check status, send reminders, and retrieve the final PDF.

Step 4: Send for Signature

PandaDoc has a separate POST /documents/{id}/send endpoint that emails the proposal to the recipient. Pass the contact's email from your CRM data and a custom message. The platform handles the email, the signing interface, and the audit trail.

If you are using DocuSign, the equivalent is creating an envelope via POST /envelopes with the document bytes and recipient details, then setting the envelope status to "sent".

Step 5: The Follow-Up Sequence

This is where most manual processes break down. After sending the proposal, teams forget to follow up consistently, especially when managing multiple deals.

Build a second N8N workflow triggered by a Schedule node that runs every morning. It polls PandaDoc's GET /documents endpoint for all proposals with status "document.sent" (meaning sent but not yet signed) and checks how many days have elapsed since the send date.

• Day 2 (viewed, not signed): Send a light follow-up via Gmail — "Happy to answer any questions before you review the proposal."
• Day 5 (not viewed or not signed): Send a stronger follow-up with a deadline — "Wanted to make sure this didn't get buried."
• Day 10 (no response): Update the CRM deal stage to "Follow-Up Required" and notify your sales rep on Slack to call the prospect directly.

These emails go out from your Gmail account (via the N8N Gmail node) so they look personal, not automated. The prospect sees a message from your sales rep's address, not a generic noreply system.

Step 6: Handle the Signed Contract

Configure a PandaDoc webhook (or DocuSign webhook) that fires when a document status changes to "document.completed". In N8N, set up a Webhook node to receive this event.

When the webhook fires, the workflow should:

1. Download the signed PDF via the PandaDoc API
2. Upload it to Google Drive in the appropriate client folder using the Google Drive node
3. Update the CRM deal stage to "Closed Won" via the HubSpot or Pipedrive node
4. Post a Slack message to your #deals channel: "New signed contract: [Company Name] — [Deal Value]"
5. Trigger your client onboarding workflow by calling a second N8N webhook

The onboarding trigger is the most valuable part. Instead of a salesperson manually handing off a new client to the operations team, the signed contract event automatically kicks off whatever comes next: sending a welcome email, creating a project in your PM tool, scheduling the kickoff call. You can read more about that in the N8N customer onboarding automation guide.

Manual vs. Automated Proposal Workflow

Common Pitfalls and How to Avoid Them

Dynamic pricing blocks

If your proposals have tiered pricing or scope options, a simple template with static variables will not work. You need conditional logic in the workflow. N8N's IF and Switch nodes let you select different template IDs based on deal type, or pass different variable sets based on the service package. Map this out before you build — the N8N logic is straightforward once you know the rules.

CRM data quality

Automated proposals are only as good as your CRM data. If reps leave fields blank, the proposal template will have empty placeholders. Add a validation step in N8N using an IF node that checks whether required fields are populated before calling the PandaDoc API. If validation fails, send a Slack message to the rep asking them to complete the deal fields before the proposal can go out.

Multiple signers

Deals that require two or more signatures (both a manager and a director, for example) need a different PandaDoc API call structure. The recipients array in the document creation request can include multiple entries with different roles. PandaDoc handles the signing order automatically based on the routing you specify in the template. Set this up in the template, not in the workflow, to keep the N8N logic simple.

Error handling

API calls fail. Documents sometimes fail to create. Add an Error Trigger node in N8N that routes failed workflow executions to a Slack alert or a log entry in Google Sheets. Without this, a failed proposal creation goes unnoticed and the deal sits in limbo.

You can read a detailed breakdown of N8N error handling patterns in the N8N error handling best practices guide.

Integrating With Your Lead Scoring Workflow

Proposal automation pairs naturally with lead scoring. If you have a lead scoring workflow in N8N, you can add a condition before the proposal step: only trigger the automated proposal for deals above a certain score threshold. High-value deals get the automated proposal plus a personal Slack nudge to the sales rep. Lower-score deals might get a shorter proposal template or a different follow-up cadence.

This kind of conditional branching is where N8N outperforms dedicated proposal tools. You have full control over the logic, and you can connect it to every other system in your stack without paying per-seat fees for another SaaS product.

What to Expect in Terms of Time and Cost

Building this workflow from scratch takes one experienced builder one to two days if you have clean CRM data and a finished proposal template. The steps that take the most time are usually the CRM trigger configuration (getting the right fields in the webhook payload) and the PDF storage and naming conventions.

Running costs are minimal. N8N cloud at the Growth tier ($20 per month) handles the executions. PandaDoc's Business tier ($49 per user per month) includes API access and unlimited templates. DocuSign pricing varies but starts higher. If you are sending twenty to fifty proposals per month, the combined tool cost is well under $100 per month and the time savings easily run to ten or twenty hours per month.

For a more detailed cost model specific to your deal volume, the ROI calculator lets you input your proposal volume and average deal value to see what the automation is worth in recovered time and improved close rates. For a broader readiness check, the AI readiness assessment helps you see which other workflows in your business are ready for automation at the same time.

Our N8N automation service handles this build end to end for clients who would rather skip the setup and get straight to the results. The workflow above is one we have built and refined across multiple client deployments.

Ready to Get Started?

Book a free 30-minute discovery call. We'll identify your biggest opportunities and show you exactly what AI automation can do for your business.

Book a Free Discovery Call

Suyash Raj Founder of rajsuyash.com, an AI automation agency helping SMBs save time and scale with AI agents, N8N workflows, and voice automation.