Route requests between projects with router workflows

A router project takes an incoming message and decides which of your other Tensic projects should answer it. You design the decision as a visual flow in the Router IDE: nodes for the steps, and block-based logic for the conditions. Use a router when one entry point (a widget, an app, an API client) must serve several specialised projects, for example a support agent and a knowledge-base project.

What a router project does

• A router is one of the project types in Tensic, next to agent, RAG and inference projects. It needs no model of its own: it calls other projects and returns their answer.
• The flow is drawn left to right: an input node receives the user's message, logic nodes decide the path, Call project nodes pass the message to other projects, and an Output node returns the answer.
• Conditions are built with visual logic blocks (in the style of Scratch/Blockly) instead of typed expressions, so the flow can be read and changed without writing code.
• Tensic converts the finished flow into an internal workflow language and runs it with its own interpreter. The generated code is not shown to you; you edit the flow only through the IDE.
• Routers can chain several projects, for example: translate the input, check the customer's sentiment, then hand unhappy customers to a support project.
• A router flow may loop back on itself by design. Build any loop with a clear exit condition.

Create a router project

1. In the sidebar, open Projects and start a new project from scratch.
2. Enter a Project name and choose the Team the project belongs to.
3. Under Type, select Router ("Build the logic visually. No model needed.").
4. Click Create project.

The project type is fixed once the project is created; a project cannot be converted to another type later. The router project gets the same tabs as other projects (Overview, Configuration, Integrations, Orchestration, Routines, Access, Guards, Budget & Limits, Logging), so budgets, access and logging work the same way.

Build a router flow in the Router IDE

1. Open the router project and click IDE in the project header. The Router IDE opens with an input node and an Output node.
2. From the Add node panel on the left, add the nodes the flow needs:
   • Condition – splits the flow into a True and a False branch.
   • Call project – sends the message to another Tensic project and passes on its answer.
   • Set variable – stores a value for later nodes.
   • Logic – a free logic block.
   • Output – the answer returned to the caller.
3. Connect the nodes by dragging from one node's output handle to the next node. Connect each branch of a Condition to its own Call project node, and connect those to Output.
4. In each Call project node, select the target project.
5. Use Tidy layout (bottom of the node panel) to rearrange the canvas.
6. Click Save flow. The header shows Unsaved changes until you save.

Use Export to download the flow and Import to load one, for example to copy a router between projects or environments. Back to project returns to the project page.

Define a router condition with logic blocks

Click a Condition node to open its block editor. The editor has one slot, Take the True branch when, and a block palette with the categories tensic.ai, Logic, Math, Text, Lists and Variables.

1. Drag the blocks for your test into the Take the True branch when slot. For example, to route greetings:
   • From tensic.ai, take Get Input (the user's message).
   • From Logic, take a comparison block and set it to =.
   • From Text, take a text block and type hello.
   • Assemble them as Get Input = "hello".
2. Alternatively, click Generate in the condition editor and describe the test in plain English.
3. Click Back to flow to return to the canvas, then Save flow.

If the test evaluates to empty, false, 0 or no, the flow takes the False branch. A condition with an empty slot therefore always takes False; the IDE warns about this with a Worth a look banner.

Generate a router flow from a description

1. In the Router IDE, click Generate with AI.
2. In Generate workspace with AI, choose:
   • Start over – build a new flow from the description; the current flow is replaced.
   • Add to it – extend the current flow.
3. Describe the routing in plain English, for example: if user input is equal to "hello" call project "test_agent" otherwise call project "test_rag".
4. Click Generate. The platform's system LLM builds a starter flow with the nodes, the condition blocks and the connections.
5. Review each node and condition, adjust if needed, and click Save flow.

Use exact project names in the description so the generated Call project nodes point to the right projects.

Test a router flow in the Router IDE

1. Save the flow first. Test runs use the saved flow, not unsaved edits.
2. Type a message in Send a test message through the flow… at the top of the IDE.
3. Click Run.
4. Read the result:
   • Answer shows what the router returns.
   • A row of chips shows each node that ran, with its duration (for example user message, condition, the called project, output).
   • On the canvas, the path that was taken is highlighted, and each node shows its output.
5. Send different messages to check that every branch reaches the intended project.

Monitor router calls in Observability

Every router call is logged like any other project call, including the calls the router makes to other projects and the models they used.

• Open the router project and click Logs to see its requests.
• Open the called project's Logs to see how it handled the forwarded message.
• Use Observability in the sidebar for the platform-wide view of calls.

Use these logs to check which branch a message took and which model answered it.

Common questions