Channels
Weik.io 2026.2Integrations publish events into a channel of their project and receive them from it with two kamelets. Product page · Video
Watch: The channel: one integration publishes, another reacts, 3:49
The video has one integration publish to a channel and another react to it.
This part of the video couldn't be loaded.
Integrations exchange events through the channels of their project, such as invoice-created. A route publishes into a channel with the weikio-event-sink kamelet and receives its events with weikio-event-source. Either way the route gives only the channel’s name.
Declare the channel#
apiVersion: weik.io/v1
kind: event-channel
metadata: { name: invoice-created, project: finance }
spec:
description: One event per invoice created in the ERP, JSON body$ weikio apply -f ./finance/events/Applying a channel without a type creates it in every environment without a build or a deployment. Each environment keeps its own events, so a reader in devtest gets only devtest’s events.
To create the same channel without a file, run weikio channel create finance/invoice-created --description "One event per invoice created in the ERP". A route that uses a channel its project hasn’t declared doesn’t start. To declare the channel, run the weikio channel create command in the route’s error message.
Publish into it#
The last step of the export route publishes each invoice:
- route:
from:
uri: direct:publish
steps:
- to: "kamelet:weikio-event-sink?channel=invoice-created"The step finishes once Weik.io has stored the event. When Weik.io can’t store it, the exchange fails and goes to the route’s error handling.
An event’s body and headers together can be at most 1 MiB.
Read from it#
Another integration starts its route from the channel:
- route:
from:
uri: "kamelet:weikio-event-source?channel=invoice-created"
steps:
- to: "{{archive-url}}/invoices"Weik.io creates a durable reader for the integration when you deploy it. The integration gets every event published from its first deploy on, including those published while it was stopped. An event counts as handled once the route has finished it. Delivery and CloudEvents explains what happens when the route fails.
Several readers#
Any number of integrations can start from the same channel. Each one gets a separate reader and works at its pace, so adding another reader later changes nothing for the others.
The copies of one integration share its reader, so two agents running the archiver handle each event once between them.
$ weikio get readers finance/invoice-created --env productionFor each integration that receives the channel’s events, weikio get readers shows the state of its event delivery:
- Whether its delivery is durable or live
- How many events it’s behind
- How old the oldest waiting event is
- How many events it’s working on
- How many events it’s retrying
- How many dead letters it has
- Whether it’s asking for events
Retention#
Each environment keeps events for 30 days within its size budget, so you can look at past events and send one again. For a channel that only forwards events, set retention: 0 to make it pass-through:
spec:
description: Live price ticks, nobody needs them later
retention: 0Weik.io never stores a pass-through channel’s events, so they can’t be listed or sent again. The channel’s readers get only what is published while they run.
Browse the events#
$ weikio events list finance/invoice-created --env production --since 1hSEQ STREAM TIME FAMILY SOURCE AGENT BYTES RESEND OF
48211 events 2026-09-16 13:02:11 UTC ev finance/erp-invoice-export agent-fi-02 1204 -
48212 events 2026-09-16 13:03:11 UTC ev finance/erp-invoice-export agent-fi-02 1187 -
48213 events 2026-09-16 13:04:40 UTC ev finance/invoice-files agent-fi-02 2310 -weikio events show finance/invoice-created --env production --seq 48213 prints one event with its headers and its body. To browse the events and a channel’s readers in the admin UI, open the Events page.



