I’m designing automation strategy for a client moving to Creatio 7.18.5 cloud. They have legacy systems that need integration, and I’m debating between native Creatio process automation versus deploying RPA bots (UiPath/Automation Anywhere) to handle the integrations.
Native workflows can trigger based on entity events and handle most business logic, but some legacy systems have no APIs - they’re mainframe green screens that require UI automation. On the other hand, managing external RPA infrastructure adds complexity and cost.
What’s your decision framework for choosing between native workflow triggers versus RPA bot orchestration? When does the integration complexity justify bringing in RPA versus building everything in Creatio’s process engine? Looking for real-world experiences from teams who’ve made this choice.
Don’t forget about the hybrid approach - Creatio 7.18 has decent RPA integration capabilities. You can call RPA bots from within Creatio process flows using the Integration Hub. This lets you use native workflows for the main process logic and only invoke RPA for the specific steps that require UI automation. We do this for a procurement process: Creatio workflow handles approvals and business rules, but calls an RPA bot to submit orders in the legacy purchasing system that has no API. Best of both worlds without overcomplicating the architecture.
Start with native Creatio workflows for everything that has an API or database access. Only bring in RPA when you absolutely need UI automation for systems with no other integration option. RPA bots are brittle - UI changes break them, they require dedicated infrastructure, and they’re harder to maintain than native workflows. We use RPA for maybe 10% of our automation needs, and only when there’s literally no other way to access the system.
The native workflow versus RPA decision should follow a structured evaluation framework based on three key dimensions that I’ve refined over multiple enterprise implementations.
Native Workflow Triggers - Optimal Use Cases:
Use Creatio’s process automation when the business process is Creatio-centric and involves:
- Entity lifecycle management (case creation, opportunity progression, service requests)
- Business rule enforcement within Creatio data model
- Integration with systems that have REST/SOAP APIs or database access
- Processes owned by business analysts who can maintain low-code workflows
- Real-time event-driven triggers (record created, field changed, timer-based)
Creatio workflows excel at orchestrating business logic where data lives primarily in Creatio and external systems are accessed via standard integration patterns. The process engine is robust for decision logic, parallel approvals, escalations, and SLA management.
RPA Bot Orchestration - When Complexity Justifies It:
Deploy RPA bots when you encounter:
- Legacy systems with no API and no database access (mainframe green screens, Citrix apps, desktop applications)
- Processes that span multiple disparate systems where Creatio is just one participant
- High-volume repetitive tasks that require complex UI navigation and data extraction
- Existing RPA infrastructure and expertise in the organization
- Need to automate vendor/partner systems you don’t control
The key insight: RPA should complement Creatio, not replace it. Use Creatio as the process orchestrator and RPA as the execution layer for specific steps that require UI automation.
Integration Complexity - Hybrid Architecture:
For your scenario with mainframe systems, I recommend a hybrid approach:
-
Process Orchestration Layer: Creatio workflows manage the end-to-end business process, including business rules, approvals, notifications, and data persistence.
-
Integration Layer: For systems with APIs, use Creatio’s native integration tools (web services, oData, Integration Hub). For mainframe green screens, deploy targeted RPA bots.
-
Bot Invocation Pattern: Creatio workflows call RPA bots as services using the Integration Hub. The workflow passes parameters to the bot, waits for completion, and processes the response. The bot is a black box that handles the UI automation.
-
Error Handling: Implement robust error handling in both layers. Creatio workflow should handle business exceptions (approval rejected, invalid data). RPA bot should handle technical exceptions (system unavailable, UI changed) and return structured error responses.
Decision Matrix:
- API available → Native Creatio integration
- Database access possible → Direct DB integration via connectors
- UI automation required + low volume → Consider building API wrapper
- UI automation required + high volume → RPA bot
- Complex multi-system process + existing RPA capability → RPA orchestration
- Creatio-centric process + limited RPA skills → Native workflows
Cost-Benefit Analysis:
RPA infrastructure (licenses, servers, maintenance) typically costs $50K-150K annually for enterprise deployments. Only justify this if:
- You have 5+ processes requiring UI automation
- Volume justifies automation (>1000 transactions/month)
- Manual effort savings exceed $200K annually
- Existing RPA investment can be leveraged
For your client, I’d recommend starting with native Creatio workflows for 80% of automation needs, and deploying targeted RPA bots only for the mainframe interactions that absolutely require UI automation. Use Creatio Integration Hub to invoke bots as services, keeping Creatio as the central process orchestration platform.
I disagree with the ‘RPA as last resort’ mindset. Modern RPA platforms like UiPath have robust orchestration, error handling, and monitoring. For complex multi-system processes that span Creatio and 5-6 other applications, RPA bots can be more maintainable than trying to cram everything into Creatio workflows. The key is proper architecture - use Creatio as the process orchestrator that calls RPA bots as services, rather than having bots initiate processes. This gives you the best of both worlds: Creatio’s business process management with RPA’s ability to interact with any system.
Consider the operational model too. Native Creatio workflows are maintained by business analysts using low-code tools. RPA bots typically require developers with specialized RPA skills. If your client has strong RPA capabilities in-house, leveraging that makes sense. If they’re primarily a Creatio shop with limited RPA expertise, stick with native automation and find API-based solutions for the legacy systems. Sometimes it’s worth building a thin API wrapper around a mainframe system rather than deploying RPA infrastructure just to avoid that investment.
The decision comes down to who owns the process. If the business process is core to Creatio (like case management, opportunity flow, service delivery), keep it in native workflows. If the process primarily lives in another system and Creatio is just a participant, RPA makes sense as the orchestrator. We had a scenario where invoice processing started in SAP, needed approval in Creatio, then posting back to SAP. We tried building it all in Creatio workflows but it became a maintenance nightmare. Switched to UiPath orchestrating the entire flow, with Creatio just handling the approval step via API. Much cleaner architecture.