Use case · Operations
Event-driven operations.
An agent starts the moment something happens: an alert, a failed payment, a new file.
The first response no longer waits for someone to notice. Routine steps are done in a minute. Changes still wait for a person.
How it works
Step by step.
Press play, or click through it yourself. Try the switch above the drawing.
Try it · What happens
alertagentlogsrecent deploysrunbookon-call engineerteam chat
waiting
01The agent waits. While nothing happens, it costs nothing.
01 / 06
Where it's used
One idea, many industries.
- 01EngineeringAn alert fires. The agent pulls the logs and the runbook before anyone is at a laptop.
- 02PaymentsA failed payment starts a friendly follow-up with the customer.
- 03LogisticsA delayed shipment starts a new delivery plan and a note to the customer.
- 04SecurityA suspicious login gets checked against recent activity, with a summary for the team.
How Promptise makes it work
All three parts, working together.
In code
A peek at the code.
- 01A signed webhook wakes the agent.
- 02Calls without a valid signature are refused.
- 03Only firing alerts start a run.
on_alert.pypython
from promptise.runtime import ProcessConfig, TriggerConfig on_alert = ProcessConfig( model="openai:gpt-5-mini", instructions="Investigate the alert. Follow the runbook.", triggers=[ TriggerConfig( type="webhook", webhook_path="/alerts", hmac_secret=WEBHOOK_SECRET, filter_expression="payload.status == 'firing'", ), ],)A real project you can run
Engineering
On-call incident agent
An alert wakes the agent, it investigates and follows the runbook, and risky fixes wait for a person.
A reference application with local stand-ins for the outside systems.