What is FluentGraph

March 16, 2026 · Hyderabadrocker · 0 comments
FluentGraph — Dependency Intelligence for ServiceNow Fluent
Open Source · MIT License · ServiceNow Fluent SDK 4.1.x

Your visual roadmap
for ServiceNow Fluent

Map every table, script, and relationship across your Fluent application. Know the full blast radius of any change — before it reaches production.

Get Started Free View on GitHub
One-command analysis Zero configuration CI/CD compatible
fluent-graph analyze — ITSM Application
$ fluent-graph analyze ── Scanning project artifacts... 📦 DATA SCHEMA ───────────────────────────────── Table Source File Status x_1566_seventh_account tables/account.ts ✓ active x_1566_seventh_customer tables/customer.ts ✓ active x_1566_seventh_risk_score tables/risk_score.ts ✓ active x_1566_seventh_fraud_alert tables/fraud.ts ✓ active 🔗 SCHEMA RELATIONSHIPS ───────────────────────── Source Field → Target Table Type account.owner → x_1566_seventh_customer reference fraud_alert.account → x_1566_seventh_account reference critical_account.team → sys_user_group reference ⚙️ LOGIC ATTACHMENTS ──────────────────────────── Artifact Table Trigger State bank_incident_onload incident [onLoad] active cs_incident_onload incident [onLoad] active cs_incident_onchange_caller incident [onChange] active cs_account_onchange_type x_1566_account [onChange] active Auto-close empty Changes change_request [action] review ✓ Analysis complete — 9 tables · 8 relationships · 9 scripts Output written to fluent-graph.json
The Problem

Production breaks are preventable

ServiceNow Fluent applications grow quickly. What begins as a handful of clean tables becomes a dense network of scripts, business rules, and cross-references. Without visibility into those connections, every refactor is a gamble.

Scenario A
You delete a field.
Production breaks.
Fourteen client scripts fail. Three business rules throw errors. Two dashboards go blank. You discover the full scope of the damage — at runtime, in production.
Error: Field 'caller_id' not found
at ClientScript: cs_incident_onload
at ClientScript: bank_incident_onload
+ 12 more...
Scenario B
A new developer joins.
No one knows the app.
Understanding how tables interconnect, which scripts are active, and why certain business rules exist takes days of exploration — time that should be spent shipping features.
Root Cause
ServiceNow Fluent needs a dependency graph
most critical question before any change: what else does this touch? FluentGraph is that answer — a free, one-command tool that draws a complete map of your project.
Capabilities

Everything your team needs
to ship with confidence

FluentGraph surfaces the architectural intelligence already embedded in your project — structured, queryable, and ready for automated pipelines.

Artifact Lineage
A complete inventory of every table, field, client script, business rule, UI action, and ACL — each mapped to its source file and active state.
Schema Relationships
Every foreign-key reference and table extension within your app, including links to platform tables like sys_user and incident.
Blast Radius Analysis
Run a single command to enumerate every artifact affected if you modify or remove a target table. Know the full impact before the first line changes.
CI/CD Integration
Outputs a machine-readable fluent-graph.json artifact purpose-built for automated pipeline checks. Intercept conflicts before they reach the merge queue.
Logic Attachment Mapping
Associates every onLoad, onChange, and onSubmit script with its owning table, trigger type, and active state — making dormant code visible at a glance.
Rapid Onboarding
New engineers understand the full application architecture in minutes rather than days. The entire dependency graph is a single command away.
Output

Three sections.
Complete visibility.

Run fluent-graph analyze and get a clean, readable report divided into three sections — plus a machine-readable JSON file for your pipelines.

01 — DATA SCHEMA
Your table inventory
A clean list of every custom table in your project alongside its source file and active status.
  • Table name and scope
  • Source file location
  • Active / deleted status
  • Visibility attributes
02 — SCHEMA RELATIONSHIPS
How your tables talk
Every reference field connection between tables — including links out to platform tables outside your scope.
  • Source table and field name
  • Target table (local or platform)
  • Reference type and direction
  • Cross-scope dependencies
03 — LOGIC ATTACHMENTS
Every script mapped
Each client script, business rule, and UI action listed with the table it attaches to and its trigger type.
  • onLoad / onChange / onSubmit
  • Business rules and script includes
  • UI actions and ACLs
  • Active vs inactive state
Blast Radius

Know what breaks
before you deploy

This is the capability that changes how teams approach refactoring. Before renaming, modifying, or removing any table, run one additional command against your project.

FluentGraph traverses your entire dependency graph and returns a ranked list of every artifact affected by the proposed change — client scripts, business rules, UI actions, and ACLs — along with a calculated risk level.

If the report returns zero dependencies, you can proceed with complete confidence. If it returns impact, you know exactly what to test before anything reaches production.

"Running blast radius before a major refactor revealed that deleting a custom field would have broken four client scripts, two business rules, and a UI action — all before a single line was deployed." — Eshwar Prasad Yaddanapudi, Creator of FluentGraph
$fluent-graph blast incident
🔥 Blast Radius — incident LOW RISK
ArtifactTypeTrigger
bank_incident_onloadclient_scriptonLoad
cs_incident_onloadclient_scriptonLoad
cs_incident_onchange_callerclient_scriptonChange
Total impacted: 3 artifacts  ·  client_script ×3
🔥 Blast Radius — x_1566039_seventh_account MEDIUM RISK
ArtifactTypeReason
cs_account_onchange_typeclient_scriptonChange
x_1566_seventh_fraud_alertfieldFK via account
x_1566_seventh_risk_scorefieldFK via account
x_1566_seventh_account_extfieldFK via linked_account
Total impacted: 5 artifacts  ·  client_script ×1 · field ×3
Get Started

Up and running
in under a minute

FluentGraph requires Node.js 18 or later and an initialized ServiceNow Fluent SDK project. No account, no configuration file, no API keys.

01
Install globally via npm
Install the package once and use it across all your Fluent projects. Alternatively, invoke it on-demand with npx without a global install.
$npm install -g @yesprasad/fluent-graph
02
Analyze your Fluent project
Navigate to the root of any Fluent project and run the analysis command. FluentGraph scans your artifact directory and produces a full dependency report in seconds.
$fluent-graph analyze
03
Run blast radius before any breaking change
Before modifying any table, supply its name as a target. FluentGraph returns the complete list of affected artifacts and a risk-level assessment.
$fluent-graph blast <table_name>
04
Wire into your CI/CD pipeline
The generated fluent-graph.json integrates with any pipeline. Add the step to your GitHub Actions workflow to block merges that introduce identity conflicts.
CI/CD Integration

Catch conflicts
before the merge

FluentGraph outputs structured JSON designed for automated pipeline consumption. Gate your deployments on dependency integrity without writing a single custom script.

.github/workflows/fluent-check.yml
name: Fluent Dependency Check on: [push, pull_request]   jobs:   analyze:     runs-on: ubuntu-latest     steps:       # Extract full artifact lineage       - name: Run FluentGraph         run: npx @yesprasad/fluent-graph analyze         # Block merge on identity conflicts       - name: Validate dependency graph         run: |           if grep -q '"action": "CONFLICT"' \                 fluent-graph.json; then             echo "Identity conflicts detected"             exit 1           fi

Add FluentGraph to your pipeline as a lightweight pre-deployment gate. The JSON output is structured, versioned, and parseable by any scripting environment.

  • ✓ Runs in GitHub Actions, GitLab CI, or Jenkins
  • ✓ No authentication or external network calls required
  • ✓ Structured JSON output for custom pipeline logic
  • ✓ Automatically blocks deploys with unresolved identity conflicts
  • ✓ Integrates with existing Fluent SDK toolchain workflows
Recognition

Trusted by engineers
building on Fluent

FluentGraph was built for the ServiceNow Fluent community and has been shared internally at ServiceNow after recognition from engineering leadership on the Fluent team.

"Running blast radius before a major refactor revealed that deleting a custom field would have broken four client scripts, two business rules, and a UI action — all before a single line was deployed to production. That kind of safety net changes how your team approaches refactoring."
EP
Eshwar Prasad Yaddanapudi
Creator of FluentGraph · ServiceNow Fluent Community
Audience: 55% Enterprise Engineers
The majority of readers building with FluentGraph work at organizations with 10,000+ employees — ServiceNow, Deloitte, TCS, and EY among the top companies represented.
Open Source · Free Forever

Map your application.
Ship with certainty.

Drop FluentGraph into any ServiceNow Fluent project and get your complete dependency graph in under sixty seconds.

View on npm Star on GitHub
npm GitHub LinkedIn
Built by Eshwar Prasad Yaddanapudi for the ServiceNow Fluent community
Hyderabadrocker
Building FluentGraph — open source dependency intelligence for ServiceNow Fluent. MIT licensed.
You might also like

Older posts →