Importing BPMN Processes

Import your existing BPMN 2.0 process definitions into MeetLoyd and operationalize them with AI agents.

Why Import BPMN?

Enterprise teams already have business processes modeled in tools like:

• MEGA HOPEX
• Camunda Modeler
• Signavio
• ARIS
• Bizagi

These tools all export to BPMN 2.0 XML (ISO 19510), making it the universal interchange format. Instead of rebuilding processes from scratch in MeetLoyd, you can import them directly and assign AI agents to each task.

How It Works

The import follows a three-step wizard:

1. Upload & Validate - Drop your .bpmn or .xml file
2. Preview - Review the mapped workflow, warnings, and unmapped elements
3. Assign Agents - Pick which agents handle each task (or skip and assign later)

The result is a draft workflow that you can further customize in the visual editor before activating.

Step-by-Step Guide

1. Open the Import Dialog

Navigate to Workflows and click the Import BPMN button next to "New Workflow".

2. Upload Your BPMN File

Drag and drop your .bpmn or .xml file into the upload zone, or click to browse. Files up to 5MB are supported (typical BPMN files are 50-500KB).

The system automatically validates the file:

• Well-formed XML with BPMN namespace
• At least one start event and one end event
• All elements are reachable from the start event

If validation fails, you'll see specific error messages explaining what needs to be fixed in the source tool.

3. Review the Preview

After validation passes, you'll see a preview of the mapped workflow:

• Mapped nodes - Each BPMN element converted to a MeetLoyd node type
• Agent slots - Tasks that need an agent assigned
• Warnings - Elements that were approximated or partially supported
• Unmapped elements - BPMN constructs that couldn't be imported

You can rename the workflow at this stage.

4. Assign Agents

For each agent slot, you can either:

• Select an existing agent from your team
• Leave it as a placeholder and assign later from the workflow editor

If your BPMN file uses lanes (swim lanes), the import suggests roles based on lane names to help you pick the right agent.

5. Confirm Import

Click Import Workflow to create the draft workflow. You can then:

• Open it in the visual workflow editor to fine-tune
• Assign remaining agents
• Configure webhook URLs, conditions, and timeouts
• Activate when ready

Element Mapping

Here's how BPMN elements map to MeetLoyd workflow nodes:

BPMN Element	MeetLoyd Node	What Happens
Start Event	Start	Entry point of the workflow
End Event	End	Exit point
Service Task	Agent	Placeholder for an AI agent
User Task	Human	Human-in-the-loop approval step
Script Task	Transform	Script stored as description (never executed)
Send/Receive Task	Webhook	HTTP integration placeholder
Exclusive Gateway	Condition	Conditional branching
Parallel Gateway (fork)	Parallel	Execute branches concurrently
Parallel Gateway (join)	Merge	Wait for all branches
Timer Event	Delay	Wait for specified duration
Sub-Process	Flattened	Child elements are inlined into the main flow

Conditions

BPMN condition expressions are mapped to MeetLoyd's template syntax where possible:

BPMN:     ${approved == "true"}
MeetLoyd: {{input.approved}} == "true"

Complex expressions that can't be automatically converted are preserved as comments, and you'll see a warning to configure them manually.

Gateways

BPMN gateways can serve as both a join point (multiple incoming flows) and a fork point (multiple outgoing flows) at the same time. MeetLoyd separates these into a merge node followed by a parallel/condition node, connected automatically.

Supported Export Tools

Any tool that produces standard BPMN 2.0 XML is supported. We've tested with:

Tool	Status
Camunda Modeler	Fully supported
MEGA HOPEX	Fully supported
Signavio	Fully supported
Bizagi	Fully supported
ARIS	Fully supported
draw.io (BPMN mode)	Fully supported

The importer detects the source tool from the XML metadata and handles tool-specific quirks automatically.

Limitations (v1)

Some BPMN constructs are partially supported or approximated:

BPMN Feature	Handling
Inclusive gateways	Treated as exclusive (warning issued)
Complex gateways	Treated as exclusive
Signal/compensation events	Skipped with warning
Message flows between pools	Not supported (single-process import)
Data store references	Noted in descriptions
Multi-instance tasks	Approximated as loops

All limitations produce clear warnings during preview so you know exactly what was approximated.

API Usage

You can also use the import endpoints programmatically:

Validate

curl -X POST https://api.meetloyd.com/api/workflows/import/validate \
  -H "Authorization: Bearer $TOKEN" \
  -F "file=@process.bpmn"

Preview

curl -X POST https://api.meetloyd.com/api/workflows/import/preview \
  -H "Authorization: Bearer $TOKEN" \
  -F "file=@process.bpmn"

Confirm

curl -X POST https://api.meetloyd.com/api/workflows/import/confirm \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "preview": { ... },
    "name": "My Imported Process",
    "agentAssignments": {
      "bpmn_task_1": "agent_abc123",
      "bpmn_task_2": "agent_def456"
    }
  }'

Tips

• Export as BPMN 2.0 XML - Make sure your tool exports standard BPMN, not a proprietary format
• Keep it under 100 tasks - Very large processes work but are easier to manage when split into smaller workflows
• Use lanes - Lane names in your BPMN diagram become role suggestions during agent assignment
• Add documentation - BPMN task documentation annotations become node descriptions in MeetLoyd
• Start with draft - Imported workflows are always created as drafts, giving you time to review and configure before activation

---

Next: Learn more about Workflows and how to build them from scratch.