Your team runs forty workflows. Half of them call the same API. Last quarter someone changed the staging URL in three graphs and missed seven others — and production invoices failed silently for a weekend.
That is not a “workflow problem.” It is a configuration sprawl problem. Nodlyn solves it with Global Variables: one named value, reused everywhere, updated once.
One source of truth, not forty copies
Think of global variables as shared settings for your whole Nodlyn instance — API base URLs, alert thresholds, inbox folders, feature flags, “last processed” timestamps. Set apiUrl once; every HTTP node that references it follows on the next run.
Operations teams love this because runbooks shrink: “Change the variable in Jobs → Variables → Global” beats “grep every workflow and hope.”
Less risk when people rotate
When configuration lives in one panel instead of buried in node settings, handoffs are easier. New engineers see violet-highlighted placeholders in the Inspector and know a workflow depends on shared config — not magic strings someone typed six months ago.
Workflow-scoped variables still exist when a value should stay private to one graph. Global is for what the organization agrees on.
From Studio to the factory floor
Global variables are not a Studio-only convenience. When you export a runtime agent, those values ship in the manifest and seed on startup — so edge deployments behave like the environment you validated in Studio.
Multi-workflow bundles deduplicate globals automatically: one gateway, many automations, one place to update the broker host.
Where teams use globals first
- Multi-environment URLs — flip staging vs production without editing every graph.
- Alert thresholds — facilities changes a temperature limit once; every sensor workflow respects it.
- Shared credentials references — pair with your vault strategy; stop duplicating hostnames and paths.
- Cross-workflow counters — last run ID, batch sequence, maintenance windows.
Try it in Studio
Open Jobs → Variables → Global, add a key, and use {{$var.key}} in any supported node setting. The AI Assistant can explain which connectors resolve placeholders — ask “How do I use global variables in HTTP requests?”
Technical reference (syntax, Read/Write Variable nodes, export behaviour): Global Variables in the Knowledge Base.
Stop copying configuration. Start owning it in one place.