Creating integrations in the admin UI

Getting started 2 · 4:02

You can build a Camel integration entirely in the browser, from the New integration dialog to a deployment running in devtest. Integrations made with the weikio CLI stay read-only in the admin UI until you allow editing.

Download the mp4Recorded on 2026.2

What it covers

The New integration button on the Integrations page and the kinds it offers
Changing the route's message in the browser editor
The save plan, and the version Weik.io builds from the save
Deploying version 0.1.0 to devtest with Start after deploy turned on
The same log lines in the admin UI and in the terminal
An integration made with the weikio CLI, which stays read-only in the browser until you allow editing

Commands in this video

Terminal

$ weikio logs sandbox/greeting

Transcript

0:02Integrations start as a few files. This video writes them in the browser.
0:10The browser holds the admin UI, a web application your Weik.io installation serves.
0:16The Weik.io CLI writes them from a terminal.
0:19Both write to the hub, which keeps files once saved.
0:23hello runs on agent dev, in the environment devtest.
0:27The project sandbox holds hello.
0:34The New integration button in the Integrations page header opens the dialog.
0:39The dialog asks which project the integration belongs to and what it's called:
0:44sandbox and greeting.
0:46The kind decides what the integration will do.
0:49Camel integration runs Camel routes.
0:52The dialog also prints the CLI command that writes these files in a folder.
1:00Continue opens the editor with the three files weikio init would write:
1:05greeting.camel.yaml, application.properties and integration.yaml.
1:12The open route runs on a five-second timer and logs whatever message it's handed.
1:20None of these files reaches the installation until you save.
1:28The route's message comes from this file.
1:31The line now reads message=hello from the browser.
1:35Pressing Save first shows a plan, before anything is written.
1:39The plan lists the three files as added, because none existed before.
1:44The dialog also prints the CLI command for the same save.
1:51Writing the save carries the files to the hub.
1:58The version the Save dialog promised now exists.
2:04The hub keeps greeting's three files, under the project sandbox.
2:09The save built greeting as version 0.1.0.
2:17A version starts by being deployed into an environment.
2:20This dialog was opened for devtest.
2:23The Version field holds 0.1.0, and Start after deploy is on,
2:28so the version runs as soon as it's deployed.
2:32The Overview already carries the message in its Latest log lines,
2:36arriving every five seconds.
2:41The deploy puts the version on agent dev, in devtest.
2:45The page confirms the deploy.
2:48greeting's deployment now runs on that agent at 0.1.0.
2:53Each tick under the card is a new log line.
2:58The CLI reads the same lines with weikio logs sandbox/greeting.
3:04The terminal reads greeting, the integration the browser made.
3:12A note marks hello's files as applied by hand with the CLI.
3:16The buttons copy hello into a new integration, or allow editing.
3:22The confirmation warns the next apply from the folder replaces what you change here.
3:30hello stays read-only until you allow editing.
3:37greeting was written, built and saved without leaving the browser.
3:42The hub keeps it under the project sandbox, at version 0.1.0.
3:48devtest runs it on agent dev, logging hello from the browser every five seconds.

Next in this track

Getting started 3 · 2:59 Connecting the Weik.io CLI