Build Process Automation workflow configurations with human tasks, gateways, and notifications.
Last verified: May 2026
Build Process Automation workflow configurations with human tasks, integration steps, gateways, and notifications.
Required Fields
compartmentIddisplayNameprocessConfig.processTypeprocessConfig.activitiesOutput will appear here...Build Process Automation workflow configurations with human tasks, gateways, and notifications. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.
The tool produces syntactically valid configurations based on current OCI service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.
Your team's expense approval process is currently emails + spreadsheets — slow, error-prone, no audit trail. The builder generates a Process Automation workflow: employee submits expense, system routes to manager (level 1 approval), if amount > $5K route to director (level 2), notifications at each step, SLA escalation if approval pending >48 hours, all actions logged for audit. Approval cycle time drops from days to hours; complete audit trail satisfies SOX requirements without manual paperwork.
The builder constructs OCI Process Automation workflow definitions: process resource (BPMN-style workflow with start event, sequence flows, gateways for branching/joining, human tasks with assignment rules, service tasks calling REST/Functions, end events), task assignment policies (user/group/dynamic), notification configuration (email + Slack on task creation/escalation), and SLA timers. Output is generated as oci opa commands and Terraform oci_opa_opa_instance + process definitions.
OCI Process Automation is the right answer for HUMAN-IN-THE-LOOP workflows (approval chains, expense reports, onboarding flows). It's NOT a fit for high-volume API orchestration — for that, use OCI Functions or Integration Service. Match the tool to the workflow type.
Human tasks need clear assignment policies. Round-robin to a team is fine for general queues; targeted assignment (e.g., 'route to current employee's manager') is better for approval flows. The system supports both; design intentionally rather than defaulting to round-robin.
Notifications integration is critical — without explicit notification sends, users won't know they have pending tasks. Wire up email + Slack notifications for every task assignment AND for SLA breaches (task pending too long). Otherwise, tasks pile up uncompleted.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.