IR Flows.
How Friday Automates
IT Incident Response.
Stop letting Tier 1 issues consume all your team’s time and resources. Train Friday on how to handle them — through easy, no-code workflow automations that keep you ahead and in control.
Request a Demo Explore the Friday Dashboard
What Are IR Flows?
Short for Incident Response Flows, IR Flows are Friday’s configurable, no-code automation workflows.
They are the mechanism that turns Friday from a detection tool into an ideal IT sidekick. Every IR Flow is built around three core components — mirroring the exact tile structure you see on the Friday canvas.
Start tile
The event that starts the flow.
Triggers are the incidents Friday detects automatically — any deviation from your environment’s established baseline. The moment a trigger fires, Friday is already on it.
Example: A device goes offline. Friday detects it instantly and the IR Flow begins — no alert sent to your team, no ticket opened. Friday handles it first.
Action tile
Friday’s corrective response.
Actions are what Friday does when a trigger fires. You configure the corrective step, how long to wait before executing it, and whether approval is required before Friday acts.
Example: Power cycle the offline device. If approval is required, Friday pauses and notifies your designated approver before proceeding — always under your control.
Result tile
The verification step.
After executing an action, Friday checks whether the issue was resolved. If yes — Friday notifies your team with a full resolution summary. If no — Friday triggers the next action or escalates. Whatever you decide.
Example: Device back online — Friday sends a full resolution summary with diagnostic details. Still offline — Friday opens a support ticket automatically with everything your team needs to know.
How It Works
From Anomaly to Resolution.
Every IR Flow follows the same intelligent logic — turning unpredictable incidents into predictable outcomes.
Anomaly detected
Any deviation from your environment’s established baseline. Friday identifies it in real-time.
Automated root cause analysis
Friday diagnoses what caused the issue before taking any action.
IR Flow triggers
Friday executes the corrective action your team pre-configured — wait time, approval, and action type all defined by you.
Verification
Friday checks against the baseline to confirm the environment is back to normal.
If resolved ✓
Friday sends a full resolution summary — what happened, what Friday did, and when the issue was closed.
If not resolved ✗
Friday triggers the next action in the flow, or automatically creates a support ticket with full diagnostic data attached. Whatever you decide.
The entire process — from detection to resolution summary — happens automatically. Your team gets notified when something needed attention, what Friday did about it, and whether it worked. Not a flood of alerts. A clean outcome.
What Friday Can Automate
The Complete IR Flow Service Catalog.
18 pre-built trigger types across four categories. Every item is configurable — set wait times, approval rules, and escalation paths to match your environment.
What IR Flows Actually Deliver.
Friday AI gives IT teams and MSPs back the hours they’ve been losing to Tier 1 busywork — here’s what that looks like in real numbers.
| Metric | Industry Standard | With Friday AI |
|---|---|---|
| Response Time (MTTR) | 4.8 hours | 1.6 hours — 67% faster |
| On-Site Dispatches | 1 per week average | 1 per month — 75% reduction |
| Cable Diagnostics | 2–4 hours (manual) | 10 seconds (Auto-TDR) |
| System Uptime | 98.7% | 99.96% (+1.26% gain) |
Ready to start building?
Full step-by-step instructions for building, configuring and managing IR Flows are available in the Friday AI documentation.
Friday Fits Into How Your Team Already Works.
IR Flows don’t replace your existing communication and ticketing workflows — they enhance them. Friday uses an Open REST API to integrate with any modern ITSM platform.
Communication Channels
ITSM Platforms
Integrates with any modern ITSM platform via Open REST API.
When Friday escalates an issue, the support ticket it creates isn’t a blank form — it arrives with logs, port data, ClearSight visual proof, and a complete record of every step Friday attempted. Your team starts troubleshooting with full context, not from scratch.
