Start with a wizard
Choose templates for lead routing and escalations. Define triggers, conditions and actions step by step.
Module · AgenticUltimateSee your processes.
See your processes.
Automate with purpose.
The Workflow Engine for SuiteCRM 8: model processes, set conditions, dry-run safely and publish versioned flows — transparent for sales and service.
Workflow EngineThe workflow at a glance
- 01New lead
- 02Check industry & ownership
- 03Assign a team
- 04Create an initial-contact task
Schematic illustration · Part of the CRM process
✓ Visual canvas✓ Guided setup✓ Simulation without sending✓ Versioned execution
More clarity for multi-step processes.
One shared editor: process owners describe the workflow, while IT retains control over approval and operations.
Continue visually
Connect AND, OR and NOT groups clearly. Labelled branches and default paths provide orientation.
Keep drafts under control
Auto-layout, undo/redo and saved drafts support editing. A list view complements the canvas for keyboard operation.
From draft to active workflow.
Approval is a separate step.
Define the trigger
Configure a record event, schedule or supported webhook as the starting point.
Connect conditions and actions
Bring ownership, field changes, tasks and messages into a clear sequence.
Simulate
Evaluate record snapshots and inspect the planned path. Write actions, emails and external calls are replaced by previews during a dry run.
Review and publish
Authorised approvers activate a version. Running instances remain bound to their starting version.
Follow execution
Inspect progress, waiting states and errors. Pause a flow or centrally stop new runs when needed.
Automation for everyday work.
Examples of configurable workflows adapted to your rules.
| Use case | Trigger | Process |
|---|---|---|
| Lead routing | New website lead | Check industry and region, assign a team, create a task |
| Follow-up | Quotation sent | Wait three days, check the current status, remind if appropriate |
| Service escalation | Ticket without a response | Consider service hours, raise priority, notify the responsible team |
| System integration | Opportunity won | Contact the ERP through a webhook and associate its response |
Wait, check and resume under control.
Execution runs in the background; capacity and operating limits are sized for your installation.
Persistent waiting states
Scheduled pauses are stored. A worker resumes due transactions without keeping a process open throughout the waiting period.
Consider current data
Recheck the relevant state before follow-up write actions. A transaction already completed does not need an outdated reminder.
Reconcile repeated attempts
An effect journal records completed steps. Uncertain external outcomes must be reconciled before an action is triggered again.
Your company stays in control.
Roles and operating limits are part of automation.
Focused permissions
Execution uses an assigned service account with limited permissions. The triggering user remains traceable.
Separate authors and approvers
Viewers, authors and approvers have separate responsibilities. Saving a draft alone does not make it live.
Bounded execution
Chain-depth limits and event budgets constrain recursive workflows. Pausing and a central stop support maintenance and error handling.
Migrate existing processes step by step.
Rollout takes existing AOW rules and external systems into account.
Analyse rules
Review existing workflows for transferability. Custom logic is assessed separately.
Validate in shadow mode
Compare results without executing the same production actions twice. Coordinate the switch from old rules to new ones.
Connect systems
Webhooks and HTTP actions integrate other applications. Access, replay protection and error handling are defined for each connection.
Frequently asked questions
Short answers about the editor, simulation and operations.
Do we need PHP skills?
Standard workflows are configured visually. Conditions, assignments and supported calculations are available in the editor.
Does simulation send real emails?
The dry run replaces write and external actions with previews. The simulated path remains visible.
What happens to running instances when we update a flow?
An instance retains its starting version. A newly published version applies to new runs.
Which SuiteCRM version is intended?
The design targets SuiteCRM 8.10.x. Specific supported versions and prerequisites are confirmed with the release.
Can existing AOW rules be transferred?
Existing rules can be analysed and recreated step by step. We assess custom logic separately; running both systems in parallel helps compare their behaviour.
How are permissions and approvals managed?
Roles separate design from production operation. Releases require deliberate approval; running instances remain bound to the version they started with.
Stronger together.
Explore the complementary areas of AgenticUltimate.
Help & documentation
Workflow Engine documentation
Editor, simulation and approval — documentation in the QOON Knowledge Base.
See the Workflow Engine
in your SuiteCRM?
In about 20 minutes we clarify your processes and show modelling, simulation and release in SuiteCRM 8.
Request a personal demo ↗No obligation · Matched to your SuiteCRM environment