Automated BMC Helix Change Approval Queue
Every morning, WebRun opens BMC Helix, finds change requests still awaiting approval ahead of their scheduled window, notes the risk level and affected services, drafts a Gmail nudge to each approver for you to send, and posts the sorted queue to Slack.
How do I get change requests approved before their scheduled window?
Every morning WebRun opens BMC Helix, finds change requests still waiting on an approver ahead of their scheduled window, and notes each one's risk level and affected services. It drafts a Gmail nudge to every approver for you to send and posts the sorted queue to Slack before the change board meets.
- Approvers see their pending changes before the window opens
- Overlapping change windows are caught before both go ahead
- The change board meeting starts with the list already sorted
Built for change managers · IT service management teams · infrastructure teams · service desk leads
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
www.bmc.comin a real browser with your saved login - no setup, no API keys. -
1
BMC Helix - find changes awaiting approval
bmc.com
WebRun opens BMC Helix to find changes awaiting approval. - Open BMC Helix and filter change requests to those pending approval
- Capture the risk level, the scheduled start, and the affected services for each
- Note who the request is waiting on and how long it has sat there
- Flag any two changes whose windows overlap on the same service
Done when Every change awaiting a decision is listed with its risk, window, and approver.
-
2
Gmail - draft a nudge per approver
gmail.com
WebRun opens Gmail to draft a nudge per approver. - Draft one short email per approver listing only the changes waiting on them
- Include the change ID, risk level, scheduled start, and hours remaining
- Leave every email as an unsent draft. You read it and send it yourself
- Skip approvers who already cleared their queue since the last run
Done when Each approver has a ready draft in Gmail, none of them sent.
-
3
Slack - post today's change queue
slack.com
WebRun opens Slack to post today's change queue. - Post the change queue to your change management channel
- Sort by scheduled start, with high risk changes called out first
- List any overlapping windows as a separate conflicts section
- Leave the decisions to the approvers. WebRun never approves a change
Done when The change board has today's sorted queue in Slack.
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 on its own?
No. WebRun only reads the change record and lists what is waiting. Approving, rejecting, and scheduling stay with your approvers and the change board.
Does it email approvers automatically?
No. Each approver nudge is left as an unsent Gmail draft for you to review. Nothing leaves your mailbox until you press send.
How does it spot changes that clash?
It compares the scheduled start and end of every pending change against the affected services, then lists any pair that touches the same service in the same window.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.