Automated Productboard Requester Follow-Ups
Every Monday, WebRun opens Productboard, finds the features whose status moved to released, follows the insights and notes attached to each one back to the companies and people who asked, builds a per-customer requester list in Airtable, and drafts a short note for each one in Google Drive for your team to review and send.
How do I tell customers when the feature they requested ships?
WebRun opens Productboard every Monday, finds the features that moved to shipped, and follows their linked insights back to the customers who asked. It builds a per-company requester list in Airtable and drafts a short note for each person in Google Drive, left unsent for your account owners to send.
- People who asked hear that it shipped instead of finding out by accident
- Every requester is traced from your own recorded insights, not from memory
- Account owners get the note written for them, ready to personalise
Built for product managers · customer success teams · account managers · B2B SaaS teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.productboard.comin a real browser with your saved login - no setup, no API keys. -
1
Productboard - trace shipped features to requesters
productboard.com
WebRun opens Productboard to trace shipped features to requesters. - Open Productboard and find the features whose release status changed to shipped since last week
- Open the insights and notes linked to each shipped feature
- Capture the company and person behind every linked insight, and what they originally asked for
- Skip anyone already told on a previous run
Done when Every shipped feature has its list of requesters and their original asks.
-
2
Airtable - build the per-customer list
airtable.com
WebRun opens Airtable to build the per-customer list. - Open the follow-up base and add a row per requester with their company, the feature, and their original ask
- Group rows by company so one account manager gets one list
- Mark the accounts where several people asked for the same thing
- Set each row's status to drafted, ready to send, or sent
Done when Airtable holds the requesters grouped by company with their original ask.
-
3
Google Drive - draft a note for each requester
drive.google.com
WebRun opens Google Drive to draft a note for each requester. - Create a doc per account holding a short note for each requester
- Quote what they asked for and say plainly what shipped
- Leave every note as a draft for the account owner to review, personalise, and send
- Never email a customer. WebRun writes the copy and stops there
Done when A drafted note sits in Drive for every requester of a shipped feature.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Will it email customers?
No. WebRun drafts a note per requester in Google Drive and leaves it unsent. The account owner reads it, personalises it, and sends it. No customer hears from WebRun directly.
How does it find who asked?
It follows the insights and notes linked to each shipped feature in Productboard back to the company and person they came from, so the list is built from your own recorded feedback rather than guesswork.
Will the same person be told twice?
No. Requesters already marked as told on a previous run are skipped, and the Airtable status on each row tracks whether the note is drafted, ready, or sent.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.