MuleSoft (REST)
MuleSoft·AE_HSc_MuleSoft_RestConnectorGuide
Overview
The MuleSoft REST connector integrates AlertEnterprise with MuleSoft Anypoint Platform — Salesforce's enterprise iPaaS / API mediation layer. The connector lets AE consume MuleSoft-exposed REST APIs to orchestrate provisioning + reconciliation across systems MuleSoft mediates (legacy HR systems, custom in-house apps, partner gateways).
Topology: Alert Connector Framework (ACF) → Alert MuleSoft Connector → MuleSoft Anypoint Platform → downstream systems mediated by MuleSoft.
Authentication: OAuth 2.0 client credentials against MuleSoft's API gateway.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
MuleSoft's API gateway authenticates AE via OAuth 2.0 client credentials. AE obtains a bearer token and uses it on subsequent API calls.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
MuleSoft Anypoint deployment with AE-accessible API
customerCustomer must have a MuleSoft Anypoint deployment exposing the API(s) AE will call, with the API contract documented.
OAuth client credentials for AE
customerCustomer registers AE as a client application on the MuleSoft API gateway and provides client_id + client_secret to AE.
Data fields
1 field mapped between AE Guardian and the vendor system.
| AE field | Vendor field | Description | Direction | Required |
|---|---|---|---|---|
| Mediated API Object | MuleSoft-exposed REST resource | The resource is defined per MuleSoft API contract — typically a user / role / entitlement object mediated from a backing system. Field mappings are per-deployment. | bidirectional | no |
- src/connectors/mule-soft-rest/source.pdf — p7 — Chapter 2, Connector Architecture
- src/connectors/mule-soft-rest/source.pdf — p30 — Chapter 6, Security