The quick download:
LogicMonitor and Work4Flow developed an Agent2Agent (A2A) integration that makes Edwin AI capabilities available to AI agents in ServiceNow.
-
ServiceNow AI agents can request Edwin AI context, metrics, root cause analysis, and diagnostic guidance during an investigation
-
Work4Flow provided the expertise behind the implementation and certification effort
-
Edwin AI remains the source of LogicMonitor observability intelligence as that intelligence becomes available within ServiceNow workflows
We’re introducing the Edwin AI Agent for ServiceNow, giving responders access to LogicMonitor intelligence inside Now Assist and Workspace. This integration embeds event correlation and deep AI investigation into the ServiceNow incident record, reducing the need to move between systems during triage.
Through new Agent-to-Agent (A2A) capabilities developed with Work4Flow, ServiceNow-side AI experiences can call specific Edwin AI functions as an investigation progresses. Instead of receiving one general package of context, the workflow can request the type of analysis the situation requires, whether that is a summary, supporting metrics, root cause analysis, or diagnostic guidance.
For customers using both platforms, that changes the role Edwin AI can play inside ServiceNow. Its intelligence becomes available at the point where the investigation needs it, with each request tied to a defined capability and grounded in LogicMonitor’s observability data.
Bringing Edwin AI intelligence to the point of action
ServiceNow is where many IT teams manage incidents, assign work, coordinate response, and track issues through resolution. LogicMonitor provides the observability intelligence those teams use to understand what is happening across hybrid and multi-cloud environments.
Connecting those environments matters because incident response depends on context.
An incident record alone may tell a responder what was reported and who owns it. Effective triage requires considerably more: What signals are related? What changed? Which systems are affected? What do the metrics show? What is the probable cause? What should the team investigate next?
Edwin AI is built to provide that operational context. It correlates signals across the IT environment and uses LogicMonitor’s ITOps Context Graph to help teams understand relationships, impact, root cause, and recommended next steps.
The A2A implementation extends that intelligence into ServiceNow in a more direct, capability-driven model.
Edwin AI capabilities available through A2A
The A2A implementation brings Edwin AI’s operational intelligence directly into ServiceNow, allowing ServiceNow AI agents to call on Edwin as an investigation unfolds. Capabilities include:
- Deep AI Investigation: Investigates incidents across operational data and tools, bringing relevant findings and evidence directly into ServiceNow incidents.
- AI Correlation: Connects related alerts and signals to reduce noise and identify the broader operational issue.
- Evidence-backed root cause analysis: Identifies probable root causes using the telemetry and operational context available to Edwin AI, rather than relying on an isolated alert.
- Operational context and evidence: Surfaces relevant alert and incident summaries, metrics, and correlated insights to help responders understand what happened and why.
- Service impact context: Uses relationships across infrastructure, applications, services, topology, and other operational context to help teams understand the scope and impact of an issue.
- Diagnosis and remediation guidance: Recommends next steps for investigation and remediation grounded in the available operational evidence.
Rather than treating the integration as a conventional exchange of records between two platforms, A2A allows the appropriate LogicMonitor capability to be requested based on the needs of the investigation.
A ServiceNow-side AI experience can request relevant intelligence from LogicMonitor, receive the Edwin AI response, and incorporate that context into the workflow. LogicMonitor continues to own the underlying intelligence and product experience.
The result is a cleaner separation of responsibilities: ServiceNow provides the environment where operational work is managed, while Edwin AI provides specialized observability intelligence to help inform that work.
Better agent workflows depend on better access to domain intelligence
As more AI agents enter enterprise workflows, their usefulness will depend heavily on the systems they can consult and the quality of the capabilities exposed to them.
ServiceNow has rich workflow context, including the incident record, assignment state, approvals, ownership, and process history. LogicMonitor has a different body of knowledge, including infrastructure behavior, correlated alerts, metrics, topology, and the ITOps Context Graph Edwin AI uses to interpret conditions across the environment.
A2A provides a structured way for those forms of context to work together. That matters because reproducing observability reasoning inside every downstream system would create additional models, data mappings, and maintenance overhead. With this approach, Edwin AI remains responsible for the analysis it is designed to perform, while ServiceNow can request the resulting intelligence when the workflow requires it.
For customers, the benefit is that the investigation can use deeper operational context without forcing teams to maintain another version of that context elsewhere.
The customer experience becomes more adaptive
The practical gain of this product development is less about exposing six named capabilities and more about what those capabilities allow the workflow to do.
A ServiceNow AI experience can now ask for a concise interpretation early in the incident, move into metrics when the evidence needs scrutiny, and request root cause or diagnostic guidance when the investigation reaches that point. The information available to the workflow can change with the state of the incident, which gives both responders and AI-driven processes a better basis for deciding what comes next.
“At Bell Techlogix, we’re building toward an operating model where AI takes on more of the repeatable work and our people can focus on improving the processes around it. Bringing Edwin AI’s operational intelligence into ServiceNow is a natural extension of that strategy. As agent-to-agent capabilities mature, we see an opportunity to give teams better context at the point of action, automate more of the Tier 1 workload, and scale more intelligent IT operations without scaling resources at the same rate.” — Tim Wheeler, Chief AI Officer, Bell Techlogix.
That is a meaningful extension of the original Edwin AI integration with ServiceNow. The first release brought LogicMonitor intelligence into the incident experience; the new A2A implementation makes that intelligence more granular and more directly callable as part of the workflow.
For teams already working across LogicMonitor and ServiceNow, the result is a tighter connection between investigation and execution. The incident stays in ServiceNow, while Edwin AI supplies the operational analysis required to understand it.
Building the A2A experience with Work4Flow
LogicMonitor collaborated with Work4Flow to implement the new ServiceNow-side A2A capabilities and support the certification process required to bring them to market.
Work4Flow contributed specialized experience across ServiceNow architecture, custom applications, Now Assist, integrations, and agentic AI engineering, working alongside LogicMonitor product and engineering teams to translate Edwin AI capabilities into a production ServiceNow experience.
That collaboration was particularly important because A2A sits at the intersection of an emerging agent model and an established enterprise platform with its own application, Store, QA, and certification requirements. Work4Flow provided the ServiceNow engineering depth required to navigate those constraints while LogicMonitor remained responsible for Edwin AI, the underlying observability intelligence, product direction, and customer experience.
“The real value of AI agents comes from giving them access to the right intelligence at the right moment,” said Karthik Sj, Chief AI Officer, LogicMonitor. “With A2A, Edwin AI can bring LogicMonitor’s observability context, from metrics to root cause analysis, directly into ServiceNow as an investigation unfolds. Work4Flow brought the ServiceNow and agentic AI expertise that helped us turn that vision into a production-ready experience for customers.”
Extending Edwin AI where your team already works
The original Edwin AI integration gave ServiceNow users access to LogicMonitor context without forcing a separate investigation path. A2A carries that idea further by letting ServiceNow request specific Edwin AI capabilities at the moment they become useful.
For our customers, that means richer incident context can follow the investigation instead of arriving as a fixed snapshot. For LogicMonitor, it creates a more precise way to make Edwin AI intelligence available inside the enterprise workflows where decisions are already being made.
As agent-driven workflows become more capable, that access to specialized operational intelligence will matter as much as the agents themselves.




