All templates

Automated commonsku Proof Approval Follow-Up

Every morning, WebRun opens commonsku, finds every order stuck waiting on a client proof approval, drafts a follow-up email for each client, and queues those drafts in Gmail for your review. A Slack note tells you exactly how many are waiting.

Runs on WebRun · Strict Lockdown policy
Every day at 8:30 AM WebRunorchestrates each step
1 commonsku find orders awaiting proof approval
2 Gmail draft client follow-up emails for review
3 Slack notify team of pending approvals
In short

How do I automatically follow up on outstanding proof approvals for promo orders?

WebRun scans commonsku every morning for orders stuck waiting on a client proof approval, then drafts a polite follow-up email in Gmail for each client, leaving every message unsent for your review. A Slack summary shows how many approvals are outstanding and which are closest to their in-hands date.

  • No proof approval sits unaddressed overnight, reducing in-hands date risk
  • Every client follow-up is reviewed by a human before it reaches the inbox
  • Team sees a live count of outstanding approvals in Slack each morning

Built for promotional products distributors · promo account managers · order coordinators

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.commonsku.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    commonsku - find orders awaiting proof approval
    commonsku.com
    WebRun in commonsku: find orders awaiting proof approval
    WebRun opens commonsku to find orders awaiting proof approval.
    • Open commonsku and filter orders to those in a proof-pending or awaiting-approval stage
    • Capture order number, client name, client email, proof sent date, and in-hands date for each
    • Prioritize by in-hands date so the most time-sensitive orders appear first

    Done when Every order waiting on proof approval is listed with client contact and in-hands date.

  3. 2
    Gmail - draft client follow-up emails for review
    gmail.com
    WebRun in Gmail: draft client follow-up emails for review
    WebRun opens Gmail to draft client follow-up emails for review.
    • Draft a polite proof-approval follow-up email for each client, referencing the order number and in-hands date
    • Leave every draft unsent in Gmail for your review before sending
    • Do not send any email automatically

    Done when A draft follow-up email exists in Gmail for each client awaiting proof approval.

  4. 3
    Slack - notify team of pending approvals
    slack.com
    WebRun in Slack: notify team of pending approvals
    WebRun opens Slack to notify team of pending approvals.
    • Post a summary to Slack listing how many proof approvals are outstanding and which are most urgent
    • Include client name and days remaining until in-hands date for each

    Done when Team has a Slack summary of all outstanding proof approvals.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.commonsku.com
ScheduleRuns automatically on this cadence
Every day at 8:30 AM
DeliveryHow each run's result reaches you
Proof approval drafts · Gmail
OutputWhat each run produces - Gmail draft follow-up emails for each client with a pending proof, plus a Slack summary of outstanding approvals.
Drafts
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it email clients without my approval?

No. Every follow-up is saved as a Gmail draft and left unsent for you to review. Nothing goes to a client until you hit send.

How does it know which orders need a proof follow-up?

It reads the order stage in commonsku each morning and picks up any order sitting in a proof-pending or awaiting-approval status.

What if the client already approved the proof?

Orders that have moved past the proof stage in commonsku are excluded automatically from that morning's run.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.