Cross-Namespace Nexus

Temporal Nexus is a feature that enables workflows in one namespace to call operations in another namespace. Steadybase uses Nexus to coordinate between the GTM namespace and the Marketing namespace.

Why Nexus?

In a multi-team organization, different teams run their own Temporal namespaces:

• GTM namespace — Sales workflows, deal management, account operations
• Marketing namespace — ABM programs, campaign management, content distribution

Nexus allows these namespaces to communicate without sharing infrastructure or breaking isolation boundaries.

How It Works

┌─────────────────────────┐     Nexus Call     ┌─────────────────────────┐
│    GTM Namespace        │ ──────────────────► │  Marketing Namespace    │
│                         │                    │                         │
│  Drew Coordinator       │    "Is this        │  ABM Program Check      │
│  Step 8: Marketing      │     account in     │  - Check campaign list  │
│  ABM Validation         │     an active      │  - Return status +      │
│                         │     ABM program?"  │    campaign details     │
└─────────────────────────┘                    └─────────────────────────┘

In the Drew Coordinator

During the 9-step Drew Coordinator workflow, Step 8 makes a Nexus call to the Marketing namespace:

1. Drew Coordinator reaches Step 8 ("Marketing ABM Check")
2. A Nexus Operation is invoked targeting the Marketing namespace
3. The Marketing namespace executes its ABM validation logic
4. Results are returned to the Drew Coordinator
5. The coordinator integrates ABM status into the final output

Current Implementation

:::info Nexus is currently simulated in the demo environment via the checkMarketingABM() activity. The production implementation will use actual Temporal Nexus Operations for cross-namespace calls. :::

The simulated implementation returns:

{
  accountId: "acme-corp",
  inABMProgram: true,
  programName: "Enterprise Expansion Q1",
  status: "active",
  touchesRemaining: 3
}

Nexus vs. Alternatives

Nexus provides the best of both worlds: decoupled namespaces with durable request/response semantics.

Future Plans

• Replace simulated ABM check with real Nexus Operation
• Add Marketing → GTM Nexus calls for campaign-triggered workflows
• Enable Customer Success namespace for cross-team health monitoring