Skip to content
Weik.ioUniversity
Try Weik.io

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.

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 the save builds on the hub
  • 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

Commands in this video

Terminal
$ weikio logs sandbox/greeting
Transcript
  1. 0:02An integration is a folder of files that does one job.
  2. 0:09The client weikio writes them in a folder, settings file integration.yaml included.
  3. 0:15In your browser, the admin UI,
  4. 0:18the web application the hub serves, writes the same files.
  5. 0:22hello runs in devtest on agent dev, in the project sandbox.
  6. 0:31The Integrations page has a New integration button in its header.
  7. 0:36That button opens a dialog that asks for the project, the name and the kind.
  8. 0:41The kind decides what the integration is, and the dialog holds seven of them.
  9. 0:46Camel integration is chosen,
  10. 0:48and the dialog prints the client's own line for these files.
  11. 0:55The editor, where the files are changed, opens on three files.
  12. 0:59The route is open, a timer that sets a message every five seconds and logs it.
  13. 1:07The three files stand in the browser, and the hub holds nothing of them yet.
  14. 1:16This file holds the message the route logs.
  15. 1:19The line now reads message equals hello from the browser.
  16. 1:23Save first shows the plan for the files.
  17. 1:26All three files are new, so they stand under Added.
  18. 1:30The dialog prints the client command for the same save.
  19. 1:36The save sends the change to the hub.
  20. 1:43The result panel says the save is done.
  21. 1:48The hub keeps the three files as greeting.
  22. 1:51The chip carries the version the save built.
  23. 1:53The settings file names no version.
  24. 2:00Deploy runs a version in an environment, here devtest.
  25. 2:04Its fields hold version 0.1.0 and Start after deploy is on.
  26. 2:12The Latest log lines panel shows hello from the browser.
  27. 2:18The deploy arrow runs from the hub to the agent dev.
  28. 2:22The page says version 0.1.0 of sandbox/greeting is deployed to devtest.
  29. 2:30The card that fills in is its deployment.
  30. 2:32A new log line arrives every five seconds.
  31. 2:38The client prints the same lines.
  32. 2:40The integration in the terminal is the same greeting the browser made.
  33. 2:52hello's Source section shows its files and the note above them.
  34. 2:56The note reads Applied by hand.
  35. 2:59The second button opens this confirmation, and the click lands on Cancel.
  36. 3:08An integration made with the client stays read-only in the browser.
  37. 3:16The browser writes the three files, and the save stores them.
  38. 3:20The hub holds greeting in project sandbox at version 0.1.0.
  39. 3:27Devtest runs the version on agent dev,
  40. 3:29and the deployment writes a log line every five seconds.

Next in this track

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