All templates

CyFrame Automatic Die Maintenance Alerts

Every Monday, WebRun opens CyFrame, checks each profile die's running hours and cycle count against its maintenance interval, logs any die that is due or overdue to a Google Sheet, and drafts a service request email to the tool room or die shop for you to review before it is sent.

Runs on WebRun · Strict Lockdown policy
Every Monday at 7:00 AM WebRunorchestrates each step
1 CyFrame check die hours against maintenance interval
2 Google Sheets log dies due for maintenance
3 Gmail draft the service request
In short

How do I know when a profile die is due for maintenance?

WebRun catches die maintenance before a die fails mid run. Each Monday it opens CyFrame, checks every profile die's hours and cycle count against its maintenance interval, logs any die due or overdue to a Google Sheet, and drafts a service request to the tool room or die shop, left unsent for your review before it goes out.

  • Worn dies are caught before they hurt profile quality
  • A service request is drafted and ready the moment a die is due
  • No die runs past its interval unnoticed

Built for plastics profile extruders · tool room leads · die shop coordinators · maintenance managers

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 cyframe.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    CyFrame - check die hours against maintenance interval
    cyframe.com
    WebRun in CyFrame: check die hours against maintenance interval
    WebRun opens CyFrame to check die hours against maintenance interval.
    • Open CyFrame and review running hours and cycle counts for every profile die
    • Compare each die against its set maintenance interval
    • Capture the die number, profile, hours run, and how far past interval for any die due or overdue

    Done when Every die at or past its maintenance interval is listed with its hours run.

  3. 2
    Google Sheets - log dies due for maintenance
    google.com
    WebRun in Google Sheets: log dies due for maintenance
    WebRun opens Google Sheets to log dies due for maintenance.
    • Open the die maintenance register and add a row for each die due or overdue
    • Record the die number, profile, hours run, and interval it has passed
    • Mark any die already flagged last week so the team can see it is still outstanding

    Done when The register shows every die due for maintenance with how overdue it is.

  4. 3
    Gmail - draft the service request
    gmail.com
    WebRun in Gmail: draft the service request
    WebRun opens Gmail to draft the service request.
    • Draft a service request to the tool room or outside die shop listing the dies due for maintenance
    • Include the die number, profile, and hours run for each so the shop can schedule the work
    • Save it as a draft for you to review. Never send the request automatically

    Done when A draft service request is ready in Gmail, unsent, covering every die due for maintenance.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
cyframe.com
ScheduleRuns automatically on this cadence
Every Monday at 7:00 AM
DeliveryHow each run's result reaches you
Maintenance register · Google Sheets
OutputWhat each run produces - A die maintenance register in Google Sheets plus a drafted, unsent service request email listing every die due or overdue.
Text
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 GUARDRAIL
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it send the service request to the die shop on its own?

No. WebRun only drafts the request in Gmail and leaves it unsent. Someone on your team reviews the die list and sends it, so no service call goes out without a person checking it first.

How does it know a die needs maintenance?

It compares each die's running hours and cycle count in CyFrame against the maintenance interval you have set. Anything at or past that interval is flagged, with how far past it is.

What if a die was already serviced this week?

It reads the live hours in CyFrame each Monday, so once a die's hours are reset after service, it drops off the due list automatically.

Put this on autopilot.

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