Templates
The integration models available in iPaaS and how to choose the right one for your case.
A template is the starting point of every integration. It defines the direction of the data, what the integration does and which steps you will configure. iPaaS currently offers three templates.
| Template | Direction | Who starts the call | Response | Requires a connector? |
|---|---|---|---|---|
| Document Creation (Inbound) | Inbound (your system → ME) | Your system | Asynchronous (202 Accepted): receipt is confirmed right away, and the final result is available in monitoring. | No |
| Document Search (Outbound) | Outbound (query to ME) | Your system | Synchronous (200 OK): the converted document comes in the response itself. | No |
| Product Search | Outbound (query to an external REST provider, through a connector) | ME, during product search | Synchronous (200 OK) | Yes |
Which template should I use?
- I want my ERP to create documents in ME (orders, invoices, suppliers, products...) → Document Creation (Inbound).
- I want to fetch an ME document and get it in my ERP format → Document Search (Outbound).
- I want to show in ME the products and offers from an external provider's catalog → Product Search.
What all templates have in common
- The same lifecycle: Draft → Needs review → Validated → Active.
- A dedicated credential per integration. See Authentication.
- The same way of running:
POST /v1/flows/{flowId}/execute. See Executions. - AI mapping to convert the data between the two sides.
- Executions recorded and searchable in Monitoring > Executions.