Sales

Proposal Signature Tracker

A proposal sitting unopened for a week is a different problem from one opened six times and unsigned, and most people chase both with the same email. This workflow tracks the document’s actual state, tells you the moment it is opened, chases differently depending on whether it has been read, and handles the signature by starting the work rather than merely celebrating.

7 stepsRequires Zapier Starter or higher25 minMedium

PandaDocHubSpotTelegramNotionDelay by Zapier

What you get

You know whether a proposal has been read before you decide how to chase it.

An opened proposal triggers a same-day, specific follow-up.

Signature starts the project rather than just ending the sale.

Workflow blueprint

When this happens

PandaDocDocument State Changed

1HU

HubSpotUpdate Deal

2TE

TelegramSend Message

3NO

NotionCreate Database Item

4DE

Delay by ZapierDelay For

5TE

TelegramSend Message

6HU

HubSpotCreate Task

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 3 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. PandaDoc has no native n8n node, so that step arrives as an HTTP Request node with the endpoint left for you to fill in.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →