Keep change requests moving before their window
Every morning, WebRun opens HaloITSM, reads the change requests on the change calendar, checks which ones are still waiting on an approval against their implementation date, logs the queue in Airtable, and sends the change manager a Telegram list ordered by how soon each window opens.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track HaloITSM change requests still waiting for approval?
Every morning, WebRun opens HaloITSM, reads the change requests scheduled in the coming days, and works out which are still waiting on an approval. It logs the queue in Airtable and sends the change manager a Telegram list ordered by implementation date, so no change reaches its window without sign off.
- No change reaches its planned window without a decision
- High-risk changes and unassigned approvers surface first
- The change board in Airtable matches reality every morning
Built for change managers · IT service desks · infrastructure teams · managed service providers
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
haloitsm.comin a real browser with your saved login - no setup, no API keys. -
1
HaloITSM - find changes awaiting approval
haloitsm.com
WebRun opens HaloITSM to find changes awaiting approval. - Open HaloITSM and go to the change requests on the change calendar
- Filter to changes whose implementation date falls inside your review horizon
- Capture each one with its requester, risk assessment, affected services, and approval status
- Set aside the changes that are still waiting on at least one approver
Done when Every upcoming change is listed with its approval status and implementation date.
-
2
Airtable - log the approval queue
airtable.com How to Automate Airtable
WebRun opens Airtable to log the approval queue. - Write one row per pending change into your change board in Airtable
- Fill in the reference, requester, risk level, affected services, and implementation date
- Add how many days are left before the window opens
- Update rows from previous runs so approved changes drop off the board
Done when The Airtable board matches today's live approval queue.
-
3
Telegram - send the morning queue
telegram.org How to Automate Telegram
WebRun opens Telegram to send the morning queue. - Send the pending changes to your change management chat in Telegram
- Order the list by implementation date so the nearest window is first
- Call out high-risk changes and any change with no approver assigned
- Leave approving or rejecting to a person. WebRun never approves a change
Done when The change manager has today's queue in Telegram, nearest window first.
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 approve or reject changes for me?
No. WebRun only reads the change records and reports which ones are waiting. Approving, rejecting, or rescheduling a change stays with your approvers, so nothing is signed off without a human decision.
How does it decide a change is urgent?
It compares each change's implementation date against today and ranks by days remaining, then lifts high-risk changes and any change with no approver assigned to the top of the list.
What happens once a change is approved?
It drops off the next run. WebRun reads the live approval status in HaloITSM every morning, so approved changes leave both the Telegram list and the Airtable board on their own.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.