The moment it happens
Get a Slack alert when a PandaDoc proposal goes out
Every proposal or quote that's sent shows up in Slack with who sent it and to whom.
- Runs
- The moment it happens
- Apps
- PandaDoc
- AI
- Not needed
- Access
- API key
Send this to your assistant
Create a ClickRuntime automation: when a PandaDoc document is sent, post the document name, the sender and the recipient to #proposals in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A proposal that leaves PandaDoc is a promise. The sales manager wants to know that the Acme quote went out on Tuesday, because the follow-up call should be booked for Thursday. The sales rep, however, forgets to log it, the CRM stage is not updated and the prospect sits in limbo with nobody tracking when the clock started on their decision.
As soon as PandaDoc says a document has been sent, you get a Slack post with the document name so the sent time is captured. It runs when the event arrives, with no polling, which means the message lines up with the moment the client's email was delivered.
Account executives who juggle many open proposals use it to remind themselves when to follow up, and managers use it to see how much is actually going out each week.
What you get out of it
Follow up while the proposal is fresh
Knowing exactly when a proposal went out lets a rep schedule a call at the right moment, a day or two later, instead of discovering a week on that the prospect never replied.
A real count of proposals out the door
Managers can see how many documents leave each week without asking reps to report. A drop in volume appears in the channel before it appears in the pipeline numbers. That makes forecasting activity far easier for leaders.
Time stamps for your own memory
When a client claims they never received a quote, the alert shows when PandaDoc sent it. That small piece of evidence ends a lot of avoidable back-and-forth. Having it recorded protects the rep and the company in a dispute over timing.
Catch drafts that never get sent
If a rep says the proposal is out but no message appears, someone notices. The gap shows up in the same channel the team already uses, rather than during a late pipeline review.
Faster handoff to finance
When a sent document includes pricing finance needs to see, the team knows to expect a signature soon. They can prepare invoicing or provisioning ahead of the signing. Starting that preparation early shortens the gap between signature and kickoff.
How it works
What happens, step by step
When a PandaDoc document changes status, PandaDoc tells ClickRuntime straight away.
ClickRuntime only continues when the document has just been sent to a client.
It posts to #proposals in Slack with the document name, who sent it and the recipients' email addresses.
Before it runs live
- Connect PandaDoc
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other PandaDoc steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, notify
@on_event
def handle(event):
posted = 0
for item in event.json or []:
doc = item.get("data") or {}
if item.get("event") != "document_state_changed" or doc.get("status") != "document.sent":
continue
sender = doc.get("sent_by") or doc.get("created_by") or {}
to = ", ".join(r.get("email", "") for r in doc.get("recipients", []))
notify.slack(f"Sent: {doc['name']}\nFrom {sender.get('first_name', '')} {sender.get('last_name', '')} to {to}",
channel="#proposals")
posted += 1
return {"posted": posted}FAQ
Common questions
Does the alert fire when I send the same document again?
Will I be told who the recipient was?
Does it need a PandaDoc webhook?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Post signed PandaDoc deals to #saleswins
When a client signs, the team sees the rep, the document and the deal amount in Slack.
See how it worksGet a weekly list of unsigned PandaDoc proposals
Each Monday I see the proposals that have been out for over a week without a signature.
See how it worksPost new orders and sign-ups to Slack
When something happens in your shop, app or form, the details land in the right channel straight away.
See how it worksKeep exploring
Set up “Get a Slack alert when a PandaDoc proposal goes out” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
