Skip to main content
Before you use Route Builder, open a connector project that has a linked source specification, and confirm your role can see Connector Projects.

​
What is Route Builder?

Route Builder is the Connector Studio surface where you design how a connector moves a request for each operation. Mapping Workspace specifies which fields go where. Route Builder specifies the runtime path: where the call starts, how you call the vendor, where you transform the body, and related steps such as logging and error handling. In plain language, a route is the wiring for one operation:
  • Where the call starts (from)
  • How you call the vendor (HTTP, kamelet, and similar steps)
  • Where you transform the body (JOLT or XSLT)
  • Logging, error handling, enrichment, and other steps in between
You don’t invent that diagram from a blank canvas every time. After you import connectors from GitHub and run Analyse, Connector Studio stores the resulting patterns as route templates. You can then scaffold, pick a template, ask an agent, drag and drop steps, and download Java or YAML when you’re ready.

​
Route templates

Connector Studio doesn’t invent route templates from nothing. The library grows when you or your team bring in existing connectors from GitHub and let the platform analyze them.

​
Create route templates

  1. On Connector Projects, select Import from GitHub.
  2. Import a connector repository that your team already built and shipped.
  3. Run Analyse on that project so Connector Studio can read the Camel routes in the codebase.
  4. From those routes, the platform recognizes patterns and stores them as route templates.
Over time you get a library of reusable starting points, such as a GET list pattern, a create-with-validation pattern, or a Sync Hub style flow. Templates often show a short name, a pattern summary, which source connectors they came from, and a small graph preview of the steps. Browse that library under Route Templates when your role can see it. Templates are starting points, not finished connectors. You still adapt them to your project and your operation.

​
Open Route Builder

Typical path after you have a connector project and some endpoint work done:
1

Open the project

Open Connector Projects and select your project.
2

Open Routes

Go to the Routes tab, or open Route Designer from the project header if your role shows it.
3

Scaffold or open a route

From Routes, scaffold missing routes, open an existing route, or start from a route template.
You don’t need to finish every property mapping before you touch routes. Many teams scaffold routes for approved operations first, then refine mappings and transforms together. You do need a project with a source specification linked. Otherwise scaffolding has nothing to hang routes on.

​
Start from a route template

When you have (or are about to create) a route for an operation, Connector Studio can show applicable templates: patterns that look like a good fit for that kind of call. A typical flow:
  1. Pick the operation or mapping you’re working on.
  2. Browse the suggested route templates (cards with a name, pattern summary, and often a small diagram).
  3. Open a template to preview the graph and where it came from.
  4. Continue in one of these ways:
    • Instantiate or open it in Route Designer and edit yourself.
    • Select Build with AI agent so the Route Builder agent applies that template as a blueprint for your operation.
You aren’t locked into the template. The point is to stop redrawing the same from → call vendor → transform → respond shape by hand every time.

​
The Route Designer canvas

When you open a route you land in Route Designer: a visual canvas plus a palette of building blocks on the side.

​
Drag and drop

The palette lists approved Camel-style steps (HTTP caller, transform, log, set property, beans, and so on, depending on what your environment exposes). You can:
  • Drag a step from the palette onto the canvas
  • Connect steps so the flow reads in order
  • Select a node to edit its details (URL, expression, log level, and so on)
  • Rearrange nodes when the flow needs a different shape
Use the canvas when you know the steps you want, or when you fine-tune something the agent already built. You don’t need to memorize every Camel enterprise integration pattern name. Start with the pieces that match your mental model: start here, call the vendor, map the body, log for debugging, handle errors.

​
Route Builder agent

Beside the canvas you can chat with the Route Builder agent. The agent is scoped to this route and this project. The agent can help you:
  • Apply a route template or blueprint in one go
  • Add or adjust steps instead of dragging everything by hand
  • Wire transforms, properties, and vendor calls from the mappings and context already in the project
  • Explain what a route is doing in plain language
When you use Build with AI agent from a template, Connector Studio seeds a starter instruction along the lines of: study this template, then apply one coherent blueprint for this operation. You can keep chatting after that. Keep prompts concrete. The agent does better with clear goals than with vague requests. For example:
  • Build this route from the list-loans template for GET /loans. Include a vendor HTTP call and a response JOLT transform.
  • Add a DEBUG log after the vendor response so we can see the raw payload.
  • Set the vendor URL property from mambu.base.url and append /loans.
  • Add basic error handling if the vendor call fails.
  • Summarize what this route does today, then suggest the next missing step.
  • Replace the identity transform with the JOLT we already generated for this operation.
What not to expect: the agent doesn’t invent credentials, ship a pull request, or claim a build passed unless your flow actually does that. Treat it as a co-pilot for the route graph, then review the canvas yourself.

​
Download route DSL

When the route looks right, open the Code side of Route Designer (or the project-level generated or download actions, depending on where you are). You can preview and download the route output in formats such as:
  • Java (a RouteBuilder-style class you can drop into a connector codebase)
  • YAML (useful for review or Camel YAML DSL workflows)
Use download when you want to review the generated route in your IDE, compare it with a reference connector, or hand it to someone who is wiring the full connector project. A downloaded Java file for one route isn’t the entire connector by itself. Full connector materialization (project files, properties, all operations) is a broader project step. Route Builder gets you the route design and export for the flows you built. For transformation ZIPs and project-level downloads, see Transformations and generated code.

​
End-to-end path

A typical end-to-end sequence:
  1. Existing connectors land in Connector Studio through GitHub import and Analyse.
  2. The platform turns those Camel routes into route templates.
  3. In your project, you open Routes and scaffold the operations you need.
  4. You pick a template that matches the kind of call (list, create, sync, and so on).
  5. You either edit on the canvas (drag and drop) or ask the agent to apply the blueprint.
  6. You tweak until the flow matches how this connector should behave.
  7. You download Java or YAML to take the route further in code.