Workflows & Event Bus
Modules that talk to each other, so people don’t have to.
A module-wiring event bus lets one action trigger another — an invoice created automatically builds its e-invoice payload, a GRN posts stock, a payment closes the ledger entry.
“Modules don’t talk to each other, so people re-enter data.”
Imagine this
Create an invoice and the e-invoice payload appears; receive goods and stock updates; record payment and the ledger closes — via the event bus.
Walk me through itWorkflows & Event Bus, step by step
- 1
Something is saved
A user creates an invoice, receives goods or records a payment.
- 2
The event bus publishes it
The platform announces the event to interested modules.
- 3
Other modules react
E-invoice payloads are built, stock is posted, ledgers update.
- 4
Extend with API and webhooks
Connect external systems to the same events on eligible plans.
Everything inside Workflows & Event Bus
Dependency-aware module activation
Cross-module automation via events
Webhooks and REST API (plan-based)
Auto-generated, versioned Swagger docs
Questions it answers for you
The questions you would ask on a busy day — answered from live data, not last month’s spreadsheet.
Who in your team uses it
Administrator
Switches modules on with dependency checks, without breaking anything.
Developer
Integrates through documented, versioned APIs and webhooks.
Everyone
Enters data once and sees it reflected everywhere.
Workflows & Event Bus works with the rest of your business
Data flows between modules through the platform’s event bus — nothing is typed twice.
Integrates with
Every moduleWorkflows & Event Bus: common questions
Is there API access?
Professional and Enterprise plans.
Are docs available?
Yes, versioned Swagger docs.
Keep exploring
See Viamione with your own workflows
Book a tailored walkthrough. We map your processes to modules and recommend a plan.