¶ Routing Domain
The Routing domain in Fuse governs how workflows, APIs, and orchestrated services are exposed externally and internally — with full policy enforcement, runtime adaptability, and cross-domain interoperability.
It enables dynamic, secured routing of events, requests, and triggers into and out of the platform, ensuring that external interactions with workflows and systems are explainable, governed, and composable.
¶ Overview
The Routing domain allows the Fuse platform to:
- Define public or internal endpoints for workflows, APIs, webhooks, and messaging services
- Enforce security, access, and governance policies at the entry point level
- Enable dynamic routing based on runtime state, token scopes, or workflow context
- Integrate external systems seamlessly through governed, tokenized APIs
- Route requests and responses adaptively based on user, role, policy, or trigger conditions
Routing is not just about connectivity — it’s about controlled, composable access to orchestrated digital ecosystems.
¶ Key Capabilities
- Dynamic Route Registration — Create, modify, or revoke routes programmatically or via workflow orchestration
- API Gateway Integration — Govern inbound and outbound API calls securely through Fuse runtime policies
- Webhook Handling — Register and manage webhook listeners and dispatchers
- Scoped Access Control — Enforce token, role, and policy-based restrictions at route level
- External System Integration — Connect external event sources, messaging buses, and platforms to Fuse domains
- Adaptive Routing — Route based on identity, payload, domain context, or runtime conditions
¶ How Routing Interacts with Execution Layers
| Layer | Routing Role |
|---|---|
| Integration | Accepts external events, requests, and triggers |
| Automation | Routes requests into pipelines and event-driven workflows |
| Orchestration | Coordinates multi-step flows launched from external systems |
| Interoperability | Governs access, token context, and adaptive routing decisions |
Routing provides the structured, governed entry point for cross-domain execution inside Fuse.
¶ Real-World Scenarios
Receiving an external webhook from a third-party platform and launching a multi-step workflow
Publishing an API endpoint that triggers an approval workflow for a new user onboarding event
Routing external telemetry data into the Intelligence domain for AI enrichment and downstream orchestration
Enforcing token-scoped access rules on public-facing API routes based on dynamic policy evaluation
¶ Extending the Routing Domain
Use these frameworks to build and extend routing capabilities:
- Routing Framework — Define dynamic, governable API routes and webhooks
- Webhook Framework — Manage inbound and outbound webhook handlers securely
- Log Framework — Monitor and trace API interactions, webhook events, and route activities
¶ Explore More
- Workflow Domain — Build multi-step flows triggered by routed events
- Security Domain — Enforce scoped access and runtime security at entry points
- Messaging Domain — Trigger messages and inbox actions based on routed external events
- Glossary — Learn terms like dynamic routing, webhook orchestration, token-scoped APIs