How to Automate Proposal Follow-ups with n8n (2025)

You spend hours building a proposal. You send it. Then… silence. The prospect who was excited on the call goes quiet, your email sinks to the bottom of their inbox, and three weeks later the deal is dead — not because they said no, but because nobody followed up. This is the single most expensive leak in most sales processes. Studies consistently show that the majority of closed deals require five or more follow-ups, yet most reps stop after one. The fix isn't willpower. It's a system that follows up automatically, stops the moment someone replies, and pulls a human in at exactly the right time. In this guide you'll build that system in n8n.

Why proposal follow-up should never be manual

Manual follow-up fails for predictable reasons: reps get busy, they forget which proposals are outstanding, they feel awkward "nagging," and they have no visibility into whether the prospect even opened the document. Each of those is a process problem, not a discipline problem. When you automate the sequence, every proposal gets the same disciplined treatment — a nudge on day 2, a value-add on day 5, and a final "should I close this out?" on day 10 — without a single reminder living in someone's head.

The goal isn't to spam. It's to make sure a warm proposal never dies of neglect. The moment a prospect replies, the automation goes silent and hands off to your rep. That combination — relentless until engaged, human once engaged — is what lifts close rates.

The workflow at a glance

Here's the full shape of what you'll build in n8n:

1. Trigger when a proposal is sent (CRM stage change, proposal-tool webhook, or a new Google Sheets row).
2. Log the proposal to a tracking sheet with a timestamp and status open.
3. Wait to day 2, check for a reply, send follow-up #1 if none.
4. Wait to day 5, check again, send follow-up #2.
5. Wait to day 10, check again, send follow-up #3 and escalate to the rep via Slack + a task.
6. Stop instantly at any point if the prospect replies, and log the outcome.

Don't want to wire all of this by hand? The AI Commercial Proposal Generator gives you a ready-to-import n8n workflow — form → company research → PDF → email — with the follow-up sequence already built in. Import it, connect your accounts, and you're following up on autopilot today.

Step 1 — Trigger when a proposal goes out

You have three clean options depending on your stack:

• CRM stage change: Use the Pipedrive Trigger or HubSpot Trigger node to fire when a deal moves to the "Proposal Sent" stage. This is the most reliable signal because it's tied to your pipeline.
• Proposal tool webhook: Tools like PandaDoc, Proposify, or DocuSign can POST an event when a document is sent. Catch it with a Webhook node listening on a dedicated URL.
• Google Sheets row: If you track proposals in a sheet, use the Google Sheets Trigger node to fire on each new row.

Whatever the source, normalize the output into a single object: prospect_email, prospect_name, company, deal_id, rep_email, and sent_at. Every downstream node reads from this.

Step 2 — Log the proposal so nothing gets lost

Add a Google Sheets node (Append operation) that writes the proposal to a "Live Proposals" tab with status open, the send date, and a blank outcome column. This sheet is your source of truth and your dashboard — at any moment you can see every warm proposal in flight and where it stands in the sequence.

Step 3 — The timed follow-up sequence with Wait nodes

n8n's Wait node is what makes multi-day sequences possible without keeping the workflow running. It pauses the execution and resumes later — set it to "After Time Interval" and choose the gap you want.

1. Wait → 2 days. Then run the reply check (Step 4). If no reply, a Gmail node sends follow-up #1: a short, friendly "just making sure this reached you" note that restates the single biggest value point.
2. Wait → 3 more days (day 5 total). Reply check again. Follow-up #2 adds value rather than pressure — a relevant case study, an ROI figure, or an offer to walk through the proposal live.
3. Wait → 5 more days (day 10 total). Final reply check. Follow-up #3 is the polite "breakup" email: "Should I keep this open, or is now not the right time?" These often get the highest reply rate of the whole sequence.

Keep each email personalized with expressions pulling from your trigger data, e.g. Hi {{ $json.prospect_name }}, about the proposal for {{ $json.company }}…. Personalization is the difference between a follow-up and junk.

Step 4 — Stop-on-reply logic

This is the piece that keeps you from looking like a robot. Before each send, add a Gmail node (Get Many, with a search filter on the prospect's email address and after the sent_at timestamp) or an IMAP Email node to check your inbox for a reply from that prospect.

Feed the result into an IF node:

• Reply found → route to the "stop" branch: update the Google Sheets row to status replied, skip all remaining sends, and let the rep take over.
• No reply → continue to the Gmail send node for that step.

Because this check runs before every send, a prospect who replies after email #1 never receives emails #2 or #3. The automation quietly disappears the moment a human relationship starts — exactly as it should.

Step 5 — Escalate to the rep at day 10

If the prospect has gone completely dark through all three emails, don't just close the loop silently. Add a Slack node that posts to the rep (or a #proposals channel): "Proposal for {{ company }} has had 3 follow-ups with no reply — time for a call or a decision." Pair it with a task in your CRM via the Pipedrive or HubSpot node so the follow-up lives in the pipeline, not just a Slack message that scrolls away. A phone call at this stage revives more dead deals than any email can.

Step 6 — Track opens and log outcomes

Open tracking tells you whether silence means "didn't see it" or "saw it, ignored it" — two very different problems. If your email or proposal tool exposes open events, catch them with an additional Webhook node and write the open count back to your sheet. When a proposal resolves — replied, won, lost, or expired — have the workflow update the outcome column with a final Google Sheets update. Over a few weeks this log becomes a goldmine: which follow-up email drives the most replies, how many touches deals actually need, and which reps have proposals stalling.

Putting it together

The finished workflow is a single linear chain with branches: Trigger → Sheets log → Wait → Gmail reply check → IF → send or stop, repeated for days 2, 5, and 10, ending in a Slack + CRM escalation. It runs entirely on autopilot, costs nothing beyond your existing tools, and guarantees that no proposal you worked hard to create ever dies in silence again. That's not a marginal gain — for most teams, recovering even one in ten "ghosted" proposals moves the revenue needle more than any new lead source.

Ready to automate? Skip the wiring and start closing more of the deals you already earned — Get this template on Gumroad →