--- title: "SIGNL4 Integration" description: "Send and resolve SIGNL4 alerts that reach the on-call team by push, SMS, and voice, tied together by a stable per-incident External ID." url: https://flowrunner.ai/integrations/signl4 date_modified: 2026-08-01T02:40:32-07:00 --- # SIGNL4 [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Send and resolve SIGNL4 alerts that reach the on-call team by push, SMS, and voice, tied together by a stable per-incident External ID. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 2 actions · Custom auth · available [SIGNL4 website](https://www.signl4.com/) · [Platform Documentation](https://docs.signl4.com/) · Capability data verified 2026-07-14 1. A monitor or job detects a production failure 2. Agent gathers the incident title, service, and a stable External ID 3. Agent confirms the signal is a real incident, not noise 4. Agent confirms the External ID is not already open 5. Agent raises the page with Send Alert to the on-call team 6. Agent records the raised alert and its External ID 7. A page that escalates to the whole on-call team on an ambiguous signal waits for approval ## What This Integration Enables An agent can raise a mobile alert to the on-call team the moment a monitor, job, or webhook detects a failure, and reuse one stable External ID per incident so raise and close stay tied together. It can automatically close an alert and stop escalation once an upstream system reports the incident recovered, and enrich alerts with service, location, and source-system context for faster routing. Send Alert supports Single ACK, where the first responder acknowledges for the team, or Multi ACK, where every notified person must acknowledge. ### Without FlowRunner **Failures go unnoticed**: An overnight failure waits until morning for someone to spot it **Duplicate pages**: The same incident pages the team repeatedly with no de-duplication **Stale open alerts**: An alert stays open and escalating after the issue has recovered ### With FlowRunner **Immediate mobile page**: The on-call team is paged by push, SMS, and voice the moment failure is detected **De-duplicated by External ID**: One stable External ID per incident keeps repeat raises from stacking up **Auto-resolved on recovery**: Resolve Alert closes the page and stops escalation when the system recovers ## Use Case Scenarios ### Detect, page, and auto-resolve A monitoring workflow detects a failed service. The agent raises a page with Send Alert, using the incident identifier as the External ID and enriching it with the affected service and location. When the upstream monitor later reports recovery, the agent calls Resolve Alert with the same External ID, which closes the page and stops further escalation. The team is paged only while the incident is live. ### De-duplicated repeat detection A noisy check fires several times for the same underlying problem. Because the agent reuses one stable External ID per incident, SIGNL4 de-duplicates the repeated Send Alert calls rather than paging the team again and again. The on-call rotation sees one incident, not a storm. ### Team-wide escalation with a gate An ambiguous signal could be a real outage or a transient blip. Rather than paging the entire on-call team on a guess, the agent stops at the human-in-the-loop step and asks a responder to confirm before it escalates. A confirmed incident pages the team; a false alarm never wakes anyone. ## Human-in-Loop Highlight A SIGNL4 page reaches the on-call team by push, SMS, and voice all at once, and it escalates until someone acknowledges. That is exactly what you want for a confirmed outage and exactly what you do not want for a false alarm. Before the agent raises a team-wide page on an ambiguous or low-confidence signal, it pauses and routes the decision to a responder: "This signal is ambiguous. Here is the detail. Escalate to the on-call team with Send Alert, or dismiss as noise?" This is FlowRunner's human-in-the-loop pattern, where the agent stops on its own, presents the evidence, and resumes when the human answers. Clear, high-confidence failures page immediately. Ambiguous ones get a human decision before the whole team's phones light up. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 2 actions ### Alerting 2 - **Send Alert** Raises a new SIGNL4 alert that is pushed to the on-call team by push, SMS, and voice, with a stable External ID for later closing and a choice of Single ACK or Multi ACK. Optional service, location, filtering, and source-system values enrich routing and display, and the action returns the created event's identifier. - **Resolve Alert** Closes an existing alert by its External ID, resolving the alert associated with that identifier and stopping further escalation. Pass the exact External ID used when the alert was raised so that raise and close stay tied to one incident. ## Frequently Asked Questions ### What can FlowRunner do with SIGNL4? FlowRunner agents can run Resolve Alert and Send Alert in SIGNL4. ### Does connecting SIGNL4 to FlowRunner require OAuth? SIGNL4 uses a custom authentication method to connect to FlowRunner. ### Can SIGNL4 trigger a FlowRunner workflow automatically? SIGNL4 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SIGNL4?** This integration exposes SIGNL4 to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/signl4. Site index: https://flowrunner.ai/llms.txt