How to Automate Proposal Follow-Up Emails with Zapier (Step by Step)

You sent the proposal on Tuesday, it is Friday now, and the client has gone quiet. You do not want to chase too hard, and you also do not want the deal to fade because you forgot. Here is the fix: use Zapier to automate proposal follow-up emails. One Zap starts when a proposal goes out (a HubSpot deal stage, a Gmail label, or a row in a sheet), waits a few days, checks whether the client already answered, and only then writes a short follow-up draft for you to approve.

Imagine it is Monday, 9 am. Three proposals from last week are still open, and three polite, specific follow-up drafts are already sitting in your Gmail. You read each one for twenty seconds, fix a name, hit send, and get back to real work.

This page is only about the moment after a proposal is sent. If you want the general follow-up habit for any lead, read our guide to automating follow-up emails without code. If the proposal itself is the hard part, start with ChatGPT for proposal writing. Here you get the exact Zap, step by step, plus an optional AI draft step and the stop rules that keep you from nudging someone who already said yes.

Why proposal follow-ups slip

A proposal is the most expensive email you send. You spent hours on scope, price and timing. Then the follow-up depends on your memory, on a busy week, in between client calls.

The usual result is one of two things. You forget, and a warm deal goes cold. Or you remember at 6 pm, write a rushed “just checking in”, and it sounds needy. Neither is a writing problem. It is a timing problem, and timing is exactly what Zapier is good at.

The trick is to let Zapier own the clock and the checking, and keep yourself in charge of the words that leave your inbox.

The Zap in one picture

Every version of this automation has the same five parts:

1. Trigger: the proposal is marked as sent (deal stage, Gmail label, or sheet row).
2. Delay: wait a set number of days, for example 3.
3. Check: look again. Did the client reply? Did the deal move? If yes, stop.
4. Draft: create a short follow-up as a Gmail draft (or send it, for low-risk reminders).
5. Log: write “follow-up 1 drafted” back to the deal or sheet, so you can see where each proposal stands.

Zapier’s Delay tool does the waiting. Its help page uses this very example: a fixed wait before the next action, “like sending a follow-up email 1 week after a form submission” (Zapier: Add delays to Zap workflows).

How to automate follow-up emails with Zapier and HubSpot

If your proposals live as deals in HubSpot, this is the cleanest path, because the deal stage tells Zapier exactly when the proposal went out and whether anything has changed since.

Before you start, add a stage in your HubSpot pipeline called something like Proposal sent, and move the deal there when you hit send.

1. Trigger: HubSpot, Updated Deal Stage. Choose your pipeline and the stage “Proposal sent”. This trigger fires when a deal enters that stage. It watches one pipeline per Zap, so if you run several pipelines, either copy the Zap or use the Deal Property Change trigger on Deal Stage with a Filter after it (HubSpot Community thread).
2. Get the contact: HubSpot, Get Contact. If the deal data does not already carry the client’s email and first name, look up the associated contact so you have both for the email.
3. Wait: Delay by Zapier, Delay For. Value 3, unit days. Pick your own number. Many people find 2 to 4 working days feels attentive without being pushy.
4. Re-check the deal: HubSpot, Get Deal. Map the Deal ID from the trigger. This pulls the deal as it is now, three days later.
5. Stop if it moved: Filter by Zapier. Only continue if the current Deal Stage still equals “Proposal sent”. If you already moved it to Won, Lost, or Negotiation, the Zap ends here.
6. Stop if they replied: Gmail, Find Email. Search string: from:{{contact email}} newer_than:4d. Set “Successful if no search results are found?” to True. Then add a second Filter: only continue if Zap Search Was Found Status is false. Zapier documents this field for exactly this kind of check (Zapier: Search for existing data).
7. Draft: Gmail, Create Draft. To: the contact email. Subject: Re: {{deal name}} proposal. Body: your template, or the ChatGPT output from the optional step below.
8. Log: HubSpot, Create Engagement (a note on the deal) or Update Deal with a custom property such as “Follow-up 1 drafted”.

Test it once with a fake deal and your own email address as the contact. Move the test deal into “Proposal sent”, set the delay to 2 minutes for the test, and watch the draft appear. Then set the delay back to days.

No CRM? Use a Gmail label or a proposal sheet

You do not need HubSpot for this. Two simpler triggers work well for freelancers and small teams.

Gmail label path. When you send a proposal, put the label proposal-sent on the sent email. Trigger the Zap with Gmail, New Labeled Email. The trigger gives you the recipient and subject, so the Delay, Find Email check and Create Draft steps stay the same as above. The only difference is the “did it move” check: you skip the HubSpot steps and rely on the reply search.

Proposal sheet path. Keep a Google Sheet with one row per proposal: client name, email, project, date sent, status. Trigger with Google Sheets, New Spreadsheet Row. After the delay, use Lookup Spreadsheet Row on the same row and only continue if status still says “Sent”. When a client answers, you change the cell to “Replied”, and the next run stops on its own.

If your proposal tool (PandaDoc, Proposify, Better Proposals and similar) has a Zapier app, check its trigger list for a “document sent” or “status changed” event. That can replace the label or the sheet, so you never have to tag anything by hand.

Optional: let ChatGPT write the draft inside Zapier

A fixed template is fine for a first nudge. If your proposals vary a lot, you can add the ChatGPT (OpenAI), Conversation action between the reply check and the Gmail draft, and feed it the deal details. This is also how people automate email responses with ChatGPT in Zapier in general: the AI writes, Zapier moves the text to the right place.

Two honest notes first. The ChatGPT app on Zapier needs an OpenAI account with prepaid API billing, which is separate from a ChatGPT Plus subscription (Zapier: Get started with ChatGPT on Zapier). And only send the AI the facts it needs: name, project, the key number, the date. Not the whole contract.

Paste this into the User Message field and map the fields in curly brackets:

You write a short follow-up email after a proposal was sent.

Facts (use only these, never invent anything):
- Client first name: {{first name}}
- Project: {{deal name}}
- Proposal sent on: {{date sent}}
- Main outcome they asked for: {{deal description}}
- Follow-up number: 1

Rules:
- Under 90 words. Plain, warm, not salesy.
- Open with one specific line about their project, not "just checking in".
- Offer one easy next step: a 15-minute call, or a reply with questions.
- Do not mention prices, discounts or deadlines unless they are in the facts.
- If a fact is missing, write [CHECK] instead of guessing.
- Output the email body only, no subject line, sign off as {{your first name}}.

Keep the Gmail step on Create Draft while you use AI text. The [CHECK] rule makes gaps easy to spot when you skim the draft. Once you trust the output for a few weeks, you can decide per follow-up whether a send step is safe.

New to AI steps in Zapier? Our guide to Zapier AI automation shows how to add an AI by Zapier step and which plan you need for it.

The second and third nudge

One follow-up is often enough. When it is not, extend the same Zap instead of building a new one:

• Follow-up 2: after the first draft step, add another Delay For (for example 4 days), the same two stop checks, and a second draft with a different angle, such as a short answer to the most likely question about scope.
• Follow-up 3, the soft close: one more wait of about a week, the same checks, then a friendly “should I close this for now?” note. It gives the client an easy way to answer, even if the answer is no.

Stop after three. Past that point, a reminder starts to feel like pressure instead of help.

Here are three plain templates you can paste into Create Draft if you skip the AI step:

Follow-up 1 (day 3)
Hi {{first name}}, did the proposal for {{deal name}} land well? If anything in the scope or timing raises a question, reply here and I will answer it today. Happy to walk through it in 15 minutes too.

Follow-up 2 (day 7)
Hi {{first name}}, one thing clients often ask at this point is how we would start in week one. Short version: [one concrete first step]. Does that fit your plans for {{deal name}}?

Follow-up 3 (day 14)
Hi {{first name}}, I do not want to fill your inbox. Should I close the {{deal name}} proposal for now, or keep it open for later this quarter? Either answer is completely fine.

How to automate follow-ups with AI and your CRM, without losing the human part

The split that works for most desk professionals is simple. The CRM holds the truth (stage, dates, notes). Zapier handles the clock and the checks. AI drafts the words. You approve.

What to automate: the waiting, the “did they reply” check, the draft, and the log line. What to keep for yourself: anything about price changes, discounts, legal terms or a complaint. Those deserve your own thought, not a template.

Keeping the CRM itself up to date from incoming email is a different job. If that is your bigger pain, our n8n CRM automation guide covers logging emails and flagging stale deals. And if you are still on Zapier Free, our list of Zapier free plan automation examples shows which two-step Zaps fit there.

Which Zapier plan you need

Be clear about this before you build. Zapier’s Free plan allows two-step Zaps only, one trigger and one action (Zapier: What’s included in the Free plan). The proposal follow-up Zap above has a delay, a lookup, filters and a draft, so it needs a paid plan that allows multi-step Zaps.

If you want to stay on Free for now, a fair compromise is a two-step Zap: trigger on the “proposal-sent” label, action Google Calendar “Create Detailed Event” titled “Follow up: {{subject}}”. In the start time, map the email date and add +3d (Zapier date fields accept simple modifiers like that, so test it once with your own email). You still write the follow-up yourself, but you never forget it.

If you already pay for HubSpot Sales Hub Professional or Enterprise, also look at HubSpot’s own sequences tool, which handles timed follow-up emails inside HubSpot (HubSpot: Create and edit sequences). The Zap is the better fit when you are on a lower HubSpot tier, or when your proposals and emails live outside HubSpot.

Mistakes that break this Zap

• Editing the Zap while runs are waiting. Zapier says that if you switch actions, replace apps, or add or delete steps during a delay, the waiting runs will not continue. Make big changes when no proposals are in the queue, or accept that open ones need a manual nudge.
• Turning the Zap off. Delayed actions do not run while the Zap is off, and they do not catch up when you switch it back on.
• No reply check. Without the Find Email or stage check, you will one day send “any thoughts?” to a client who signed yesterday.
• Sending AI text straight to the client. Keep drafts until you have read a few weeks of output.
• Forgetting the stage move. The HubSpot path only works if you actually move deals to “Proposal sent” and out of it again. If that habit is shaky, the Gmail label path is more forgiving.

Delays also have a ceiling: Zapier holds a waiting task for up to one month (30 days), so keep your full follow-up window inside that (Zapier delay limits).

What you end up with

Every proposal you send now has a quiet assistant behind it. Three days later, if nothing has happened, a short draft waits in your inbox with the client’s name and project already in it. If the client replied or the deal moved, nothing happens at all. Your CRM or sheet shows which proposals got a nudge and when.

You still choose the words that go out. You just stop carrying the follow-up dates in your head.

FAQ

Can Zapier send the follow-up automatically instead of making a draft?

Yes. Swap Create Draft for Send Email in the Gmail step. It is reasonable for a fixed, low-risk reminder you wrote yourself. For AI-written text or anything that touches price, keep the draft step.

Does this work with Outlook instead of Gmail?

The shape is the same. Use the Microsoft Outlook app in Zapier for the search and the draft or send step, and test the search query in Outlook first so you know it finds replies from that client.

How many days should I wait before the first proposal follow-up?

There is no single right number. Two to four working days is a common starting point. If you told the client “I will check in Thursday”, set Delay Until to that date instead, so the follow-up matches your promise.

Want more short, practical builds like this one for your desk work?