Camel integrations
Weik.io 2026.2Write an integration as a folder of Camel files, publish its versions, give it variables, secrets and dependencies, choose its Camel version, add custom metrics and schedules, and decide where it runs.
On this page
A Camel integration is a folder of Camel files that you write as you would for Camel JBang, with routes in YAML, XML or Java, beans, kamelets and properties. These pages follow one integration, finance/erp-invoice-export, from its folder through versions and the values each environment gives it, to the dependencies it needs, the Camel version it runs on, the counters it reports and the agents that run it.
Pages#
Integration folders and routes An integration is a folder of Camel files in any layout, with routes in YAML, XML or Java, beans, kamelets, properties, jars and a README the admin UI shows.Versions and the developer loop
weikio apply publishes an integration as an immutable version that the hub builds once, and weikio dev run runs the folder on your machine before that.Variables and secrets Values that differ between environments are variables and secrets, which routes read as plain Camel properties and which reach each deployment at its next start.Dependencies and kamelets Camel components resolve by themselves, other libraries come from Maven coordinates or jars in the folder, and kamelets come from the folder, the platform, the project or Camel's catalog.Camel versions Weik.io 2026.2 builds and runs integrations on Camel 4.18.5 and 4.22.1, and each integration picks its line in integration.yaml or application.properties.Custom metrics Count what your integration does with Camel's micrometer: and opentelemetry-metrics: components, and read the counts beside the platform's own figures.Schedules A Camel route starts on a timer or a cron, and a schedule document runs a command, curl or a script on an agent at set times in UTC.One copy at a time An integration that two agents run can still do its work once, with singleton: true or Camel's master: component and a lock the hub keeps.Where an integration runs An integration lists its requirements, each agent has capabilities an administrator gives it, and a deployment runs on every agent that matches.Invoke a route weikio invoke and the admin UI's Invoke dialog send a message into a running route, on any endpoint whose component accepts one, and show the reply.