Events and schedules
Starts processes from business events, incoming data or a defined timetable.
Wicks
Wicks turns business rules into controlled workflows. An event in one product can start a sequence of checks, human decisions, data changes and communications in others.
Automation is not hidden in a collection of fragile connectors. Wicks makes the process explicit: what starts it, which conditions matter, where a person must decide and how the system recovers from an error.
Starts processes from business events, incoming data or a defined timetable.
Directs each case through the right branch using current business context.
Includes approvals and tasks where responsibility cannot be delegated to code.
Records progress, retries recoverable steps and makes failures traceable.
Wicks is the movement inside Wi App. It uses structures from Winity, reaches external systems through Wintera and can trigger product operations prepared by Wizio.
Receives
Organises
Returns
No. A process may combine data operations, communications, integrations, branching, approvals and recovery steps.
Yes. Human tasks and approvals are first-class stages rather than workarounds outside the system.
Execution is recorded step by step; recoverable actions can be retried and unresolved failures remain visible for investigation.