Automated Autodesk RFI Chasing
Every morning, WebRun opens Autodesk Construction Cloud, lists the RFIs and submittals that are past due or due today, drafts a short text to each responsible party in Twilio and leaves it queued for your approval, then files the day's chase log as a document in Google Drive.
How do I automatically chase overdue RFIs and submittals on a construction project?
WebRun opens Autodesk Construction Cloud every morning and lists the RFIs and submittals that are past due, with the ball-in-court owner and days late. It drafts a nudge text per owner in Twilio for you to approve, then files a dated chase log in Google Drive so the follow-up history survives to closeout.
- Late RFIs surface the morning they slip, not at the weekly meeting
- Each responsible party gets one grouped nudge instead of five
- A dated chase log builds itself for closeout and claims
Built for general contractors · project engineers · construction PMs · design build 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
acc.autodesk.comin a real browser with your saved login - no setup, no API keys. -
1
Autodesk Construction Cloud - find overdue RFIs and submittals
acc.autodesk.com
WebRun opens Autodesk Construction Cloud to find overdue RFIs and submittals. - Open Autodesk Construction Cloud and select each active project
- Filter RFIs to open and sort by due date
- Capture anything past due or due today with its number, subject, ball-in-court, and days late
- Repeat for open submittals awaiting a response
- Note any item already chased in the last two days so it is not chased twice
Done when Every overdue RFI and submittal across active projects is listed with its owner and days late.
-
2
Twilio - queue a nudge to each owner
twilio.com
WebRun opens Twilio to queue a nudge to each owner. - Draft one short text per responsible party listing their overdue items and the project
- Group several late items for the same person into a single message
- Leave every message queued in Twilio for you to review and release. Nothing sends on its own
- Flag anyone with no mobile number on file so you can chase them another way
Done when A nudge is drafted and queued for each responsible party, awaiting your approval.
-
3
Google Drive - file the daily chase log
drive.google.com
WebRun opens Google Drive to file the daily chase log. - Save a dated chase log to your project folder in Google Drive
- List each overdue item, its owner, days late, and whether a nudge was queued
- Keep one file per day so the history is auditable at closeout
Done when Today's chase log is filed in the project folder in Google Drive.
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 text subcontractors without my approval?
No. Every message is drafted and left queued in Twilio for you to review and release. WebRun never sends a text on its own, and it never responds inside an RFI thread.
Does it change anything in Autodesk Construction Cloud?
No. WebRun reads RFIs and submittals only. It does not answer, close, reassign, or edit any item, so your project record stays exactly as your team left it.
What if the same person is late on five items?
They get one message covering all five, grouped by project. WebRun also skips anyone already nudged in the last two days so nobody is chased twice for the same item.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.