Usage patterns
Integration needs boil down to a small number of patterns: a trigger, a workflow, and the target system. Recognizing the pattern that matches your need avoids reinventing the workflow structure. For configuration details, see Triggers and Workflows.
When to use what
| Pattern | Trigger | Typical use case |
|---|---|---|
| Scheduler | Scheduler | Periodic synchronizations, batches |
| File import | File | Data imports from files |
| Events | API route / Events | Real-time reactions |
| API exposure | API route | Creating calculation APIs |
Choosing according to your need
| Need | Recommended pattern |
|---|---|
| Periodic synchronization | Scheduler |
| Partner file imports | File import |
| Real-time reaction | Events |
| Simple calculation API | API exposure |
| Large batch volumes | Scheduler or File import |
| Routing to different systems | Events with Switch |
Pattern 1: Scheduler (CRON)
Triggers a workflow at regular intervals defined by a CRON expression.
Diagram
Variant with parameters
Use cases
| Use case | CRON | Description |
|---|---|---|
| Daily stock sync | 0 6 * * * | Synchronize ERP → E-commerce every morning |
| Weekly export | 0 2 * * 1 | Export to a partner every Monday |
| API polling | */5 * * * * | Check for new orders every 5 min |
Advantages of the pattern:
- Flexible configuration (CRON expressions)
- Predictable and traceable executions
- Independent of source/target systems
Pattern 2: File Import
Triggers a workflow when a file is dropped (upload, SFTP, or email).
Diagram — Whole File Mode
Diagram — Row by Row Mode
If the target system cannot absorb the rows at maximum speed, set a processing interval between rows.
Use cases
| Use case | Mode | Description |
|---|---|---|
| Catalog import | Whole file | Daily import of a CSV of 50,000 products |
| Price update | Row by row | Each row triggers an API update |
| EDI import | Whole file | Receiving partner XML files |
Pattern 3: Event Reception
Reacts in real time to events (webhooks, API endpoints, Pub/Sub).
Diagram — With Switch routing
A single entry point, multiple processings: splitting by case limits the complexity of a workflow that must react to several types of events — see the Switch node.
Diagram — Simple real time
Latency of the order of a few seconds between the event and the processing.
Use cases
| Use case | Trigger | Description |
|---|---|---|
| Order → ERP | Webhook | Automatic creation for each order |
| Stock → E-commerce | Event | Real-time synchronization |
| Payment → Notification | Webhook | Confirmation email |
Pattern 4: API Exposure
Creates HTTP endpoints for calculations or aggregations without storage.
Diagram — Simple calculation
Diagram — Multi-source aggregation
No storage, on-the-fly calculation: the API can be called by any system.
Use cases
| Use case | Method | Description |
|---|---|---|
| Shipping cost calculation | GET | Calculation based on weight and destination |
| Customer 360° view | GET | Aggregation CRM + ERP + Support |
| Data validation | POST | Validity check |
Go further
See also: Best practices