Connector Coverage

Every connector is classified by the strongest verification evidence that actually exists for it — not by how finished its generated code looks. “Implemented” and “verified” are different claims, and we keep them separate.

Tier 3

Verified against a live Mule runtime

Exercised through a real HTTP endpoint and diffed field-by-field against a running Mule instance — the strongest evidence we hold.

HTTP (listener, request)
Database / MySQL (select, insert, update, delete, bulk-insert)
File (read, write, list, move, copy)
Object Store (store, retrieve, contains, remove)
DataWeave (ee:transform)
Cache scope & invalidation
Batch (job, step, aggregator)
Core flow control (choice, foreach, scatter-gather, round-robin, try, error handling)

Tier 2

Verified against real infrastructure

Converts, compiles, and runs against the real service in a container (Docker / LocalStack) — verified end-to-end, short of a live-Mule HTTP diff.

VM
Redis
Kafka
MongoDB
AMQP / RabbitMQ
Amazon S3
Amazon SQS
Amazon SNS
Email (SMTP / IMAP)
Scheduler
File listener

Tier 1

Code-generated & unit-tested

Generated Spring Boot code asserted by unit tests. Live-infrastructure verification is on the roadmap; until then we say so plainly rather than imply more.

JMS
Salesforce
Twilio
Slack
ServiceNow
SAP
SOAP / Web Service Consumer
Anypoint MQ
LDAP
Workday
NetSuite
Azure Service Bus
FTP
SFTP
Validation
Scripting
Snowflake
Zendesk
Gmail
Google Drive
Google Calendar
Google Sheets

Anything genuinely untranslatable is never silently dropped — it lands in a Manual Fixes report with the original preserved and clear guidance for your team. (SAP uses SAP's proprietary JCo library, which you license from SAP.)

Backed by 1,724 automated tests — 457 in the converter, 1,267 in the transformation engine — with zero failures.