Skip to content
Weik.ioUniversity
Try Weik.io

Which part do I need?

Concept 3 · 3:05

Each thing you want to do has a part of Weik.io that does it, such as a transfer for moving files on a timetable or the API gateway for partners who call your systems. The video then shows several parts working together on one invoice flow.

Download the mp4Recorded on 2026.2

What it covers

  • A map of needs, with the part of Weik.io that answers each one and an example
  • A transfer that copies invoice PDFs from FTP to a storage bucket on a schedule
  • An integration that posts each invoice to the ERP's HTTP interface
  • The API gateway in the hub, with keys and call limits for partners
  • An event channel, a schedule, change tracking and the entity store
  • A webhook through the gateway into a channel, and transfer run records that start an integration

Commands in this video

This video explains with drawings and types no commands.

Transcript
  1. 0:01This video answers the question in the title,
  2. 0:04then shows the parts working together on one flow.
  3. 0:11The left column holds what you want to do.
  4. 0:14The middle column holds the part of Weik.io that answers it.
  5. 0:18The right column shows one example, and the map stays open.
  6. 0:26Every morning, supplier invoice PDFs wait on a partner's FTP server.
  7. 0:32The company wants them moved to its storage bucket.
  8. 0:35The need in plain words: move files between two systems on a timetable.
  9. 0:40The part of Weik.io that answers it is a transfer.
  10. 0:44It copies files from one place to another on a schedule.
  11. 0:48You don't write a route for a transfer.
  12. 0:54The next example is to connect two systems and change the data on the way.
  13. 0:59An integration answers it, a folder of Camel files.
  14. 1:03It posts each invoice to the ERP's HTTP interface.
  15. 1:08Another need is to let outside callers use an API with a key and a limit.
  16. 1:13The API gateway sits in the hub, in front of the API.
  17. 1:17Partners call with a key, and the limit says how often they may call.
  18. 1:22Another need is to react when something happened,
  19. 1:25without sender and receiver knowing each other.
  20. 1:28Eventing answers it with a channel.
  21. 1:30The integration above sends events into the channel,
  22. 1:33and a second integration reacts.
  23. 1:40A schedule answers the need to run a command at set times.
  24. 1:43When a database table changes, a change tracking answers it.
  25. 1:48The entity store remembers what integrations have already processed.
  26. 1:52More needs exist than the ones this drawing names.
  27. 1:59The API gateway sits in front of the integration's HTTP route or any other HTTP service.
  28. 2:06A webhook is an address that takes a call and turns it into an event.
  29. 2:11The call comes in through the gateway, and the channel stores each call.
  30. 2:15The integration on the channel reacts to the stored call like any other event.
  31. 2:20Each finished run of the transfer publishes a run record.
  32. 2:23An integration that reads the transfer's records starts when the batch has landed.
  33. 2:32A transfer copies files on a schedule.
  34. 2:35An integration connects two systems and changes the data.
  35. 2:39The gateway sits in front of the API.
  36. 2:41A channel answers the need to react to what happened.
  37. 2:45A schedule, a change tracking and the entity store answer three more needs.
  38. 2:50Every integration here is deployed into an environment.
  39. 2:54An API is deployed too, and the gateway serves it.