Skip to content

Commit ea87e2f

Browse files
authored
Add overview of Mulesoft to Azure Logic Apps integration
This document provides an overview of integrating Mulesoft with Azure Logic Apps, detailing API usage, event-driven patterns, common use cases, and EDI flows.
1 parent e4b0d50 commit ea87e2f

1 file changed

Lines changed: 81 additions & 0 deletions

File tree

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
# From Mulesoft to Azure Logic Apps - Overview
2+
3+
Costa Rica
4+
5+
[![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/)
6+
[brown9804](https://github.com/brown9804)
7+
8+
Last updated: 2025-10-23
9+
10+
----------
11+
12+
## Integration with Manhattan Active platform
13+
14+
> Azure Logic Apps doesn’t have a native connector for Manhattan Active, but they `integrate very well because Manhattan Active is API first and exposes thousands of RESTful endpoints`
15+
> for WMS, TMS, and Supply Chain Planning:
16+
> - Manhattan Active platform provides `REST APIs (JSON over HTTPS) for all its microservices.`
17+
> - Logic Apps can call these APIs using:
18+
> - HTTP `action (built-in) for GET/POST/PUT calls.`
19+
> - Custom `connector if you want reusable Manhattan-specific actions.`
20+
> - For authentication, `Manhattan typically uses OAuth 2.0 or API keys, which Logic Apps supports out of the box.`
21+
22+
> [!TIP]
23+
> - Manhattan Active’s `API-first architecture means any system that can make secure HTTP calls can integrate.`
24+
> - Logic Apps `adds workflow orchestration, error handling, retry policies, and built-in connectors for other systems (ERP, CRM, EDI).`
25+
26+
Event-Driven Patterns:
27+
> - Manhattan Active supports `asynchronous messaging via Google Pub/Sub.`
28+
> - Logic Apps `can subscribe to events by:`
29+
> - Using [Azure Event Grid](https://learn.microsoft.com/en-us/azure/event-grid/overview) or [Service Bus](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview) as intermediaries.
30+
> - Building a webhook endpoint in Logic Apps to receive Manhattan notifications.
31+
32+
| Event Grid | Services Bus |
33+
| ---- | ----- |
34+
| <img width="1002" height="186" alt="image" src="https://github.com/user-attachments/assets/6782e350-3d31-4d09-9011-5fdcebcbebe9" /> | <img width="780" height="137" alt="image" src="https://github.com/user-attachments/assets/18e7dd1e-d9e6-4d15-80c8-2465c128a7b5" /> |
35+
36+
37+
Common Use Cases:
38+
> - Order orchestration: Logic Apps `can call Manhattan APIs to create or update orders.`
39+
> - Shipment updates: Trigger Logic Apps `when Manhattan sends status changes.`
40+
> - Inventory sync: Periodically `poll Manhattan APIs or react to events for stock updates.`
41+
> - EDI ( Electronic Data Interchange) flows: Logic Apps can transform data from Manhattan into X12/EDIFACT for trading partners using Integration Account. `Refer to the automated exchange of business documents between
42+
> organizations using Electronic Data Interchange (EDI) standards. Instead of sending PDFs or emails, companies use structured formats like X12 or EDIFACT to communicate orders, invoices, shipment notices, etc.`
43+
44+
What is EDI:
45+
46+
`EDI flows are the backbone for B2B communication in supply chain, ensuring standardized, automated document exchange between systems and trading partners.`
47+
48+
<details>
49+
<summary><b> What EDI Flows Are? </b> (Click to expand)</summary>
50+
51+
An **EDI flow** is the end-to-end process of:
52+
1. **Receiving or sending an EDI message** (e.g., a purchase order in X12 850 format).
53+
2. **Validating and transforming** the message into your internal system format (JSON, XML, etc.).
54+
3. **Acknowledging** receipt (e.g., sending a 997 Functional Acknowledgment).
55+
4. **Routing** the message to the right system (ERP, WMS, TMS).
56+
5. **Tracking and logging** for compliance.
57+
58+
> Common EDI Document Types:
59+
60+
- **850** – Purchase Order
61+
- **855** – Purchase Order Acknowledgment
62+
- **856** – Advance Ship Notice
63+
- **810** – Invoice
64+
65+
> Why It Matters for Manhattan Active
66+
67+
- Your carriers, suppliers, and customers often require EDI for **orders, shipments, invoices**.
68+
- Manhattan Active handles internal processes via APIs, but external partners may still expect EDI.
69+
- Logic Apps (with **Integration Account**) can:
70+
- Convert JSON from Manhattan APIs → X12/EDIFACT for partners.
71+
- Handle **AS2/SFTP** transport for secure exchange.
72+
- Manage acknowledgments and batching.
73+
74+
</details>
75+
76+
<!-- START BADGE -->
77+
<div align="center">
78+
<img src="https://img.shields.io/badge/Total%20views-1532-limegreen" alt="Total views">
79+
<p>Refresh Date: 2025-10-23</p>
80+
</div>
81+
<!-- END BADGE -->

0 commit comments

Comments
 (0)