.png)
IFS Cloud Integration Guide
Integrate IFS Cloud with enterprise systems through REST and OData-style projections, selected business events, authenticated APIs, and scheduled workflows.
IFS Cloud integration options at a glance
IFS Cloud primarily integrates through REST APIs and OData-style projections that support querying, filtering, paging, relationship expansion, and business-object operations. Selected business events can provide notifications through configured event channels, outbound integrations, or messaging infrastructure, although coverage depends on the event and deployment. OAuth 2.0 and OpenID Connect are common authentication approaches, with permissions governed by scopes and the IFS Cloud security model. Martini can consume these APIs, receive supported HTTP notifications, orchestrate workflows, map projection payloads, apply business rules, and run scheduled incremental synchronizations. SOAP, attachments, and bulk processing require validation for the target release and projection.
| Integration point | Supported by IFS Cloud? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST and OData-style APIs | Yes | Read, create, or update Customers, Suppliers, Inventory Parts, Sales Orders, Purchase Orders, Invoices, Work Orders, and Projects when the relevant projection permits the operation. OData conventions support filtering, selection, expansion, and paging. | Martini can consume IFS Cloud REST APIs through HTTP workflows, configure authentication, transform payloads, apply validation and business rules, and handle response errors. |
| Authentication | Yes | OAuth 2.0 or OpenID Connect tokens, client credentials, and user-context tokens can be used according to the tenant identity configuration. Basic Authentication may exist in compatibility configurations. | Martini can store tenant-specific credentials and token configuration as secrets, acquire or use access tokens, and send Bearer authorization headers. |
| Business events and outbound callbacks | Limited | Selected business events may be delivered through configured event channels, outbound integrations, HTTP callbacks, or messaging infrastructure. Coverage depends on the event, product area, configuration, and release. | Martini can expose an authenticated REST endpoint or webhook-oriented workflow to receive supported HTTP notifications and can route event payloads into downstream workflows. |
| Bulk, asynchronous, and batch processing | Limited | Collection endpoints, paging, and product-specific asynchronous or bulk processing may support larger synchronizations, but no universal bulk API across all IFS Cloud objects was confirmed. | Martini can orchestrate paginated or bounded batch workflows, maintain checkpoints, limit concurrency, and retry recoverable failures with backoff. |
| File and attachment APIs | Limited | Documents and attachments are available in relevant business areas, but endpoint behavior, content format, size limits, and object relationships depend on the module and projection. | Martini can transfer binary or encoded content, call attachment operations after parent-object creation, and route file exchange through supported enterprise file services where configured. |
| SOAP APIs | Legacy | SOAP and web-service interfaces exist in parts of the IFS product landscape, but REST projections are preferred for new IFS Cloud integrations and availability must be confirmed for the target environment. | Where a specific IFS Cloud SOAP interface is confirmed, Martini can consume SOAP services and transform XML responses; otherwise REST should be the starting point. |
| Database and analytics access | Not confirmed | Direct database access should not be assumed for IFS Cloud SaaS. Supported APIs, events, reports, and exports are the preferred integration mechanisms. | Martini should use IFS Cloud APIs or approved export mechanisms rather than direct database connectivity unless access is explicitly provided and approved. |
How IFS Cloud exposes data and business events
IFS Cloud REST APIs
IFS Cloud primarily exposes RESTful APIs organized around projections. These projections provide controlled representations of business objects and may support OData-style filtering, selection, expansion, paging, actions, and functions. Available fields and operations vary by product area, version, configuration, and extensions.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the selected projection, retrieves or submits data, maps the response into a canonical model, applies business rules, and writes to the target system. The workflow should confirm projection capabilities and preserve correlation identifiers.
Implementation sequence
IFS Cloud Business Events
IFS Cloud provides business-event capabilities for selected events. Notifications may use configured event channels, outbound integrations, HTTP callbacks, or messaging infrastructure, but event coverage is not universal and depends on the event and deployment.
Martini implementation pattern
Martini implementation pattern: expose an authenticated Martini API when the deployment can deliver HTTP notifications, validate the event envelope, retrieve the current IFS Cloud object when the notification contains only an identifier, and process duplicates safely. Messaging delivery requires the supported protocol for the environment.
Implementation sequence
Scheduled IFS Cloud Synchronization
Scheduled incremental synchronization is appropriate when an event is unavailable, incomplete, or unsuitable for reconciliation. IFS Cloud collections should be processed with supported paging and a reliable timestamp or change indicator where available.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow loads the durable checkpoint, requests ordered pages using an incremental filter, transforms each object, writes idempotently to the target, and advances the checkpoint only after successful processing.
Implementation sequence
IFS Cloud Attachments
IFS Cloud supports documents and attachments in relevant business areas, but the endpoint, relationship, content format, and permissions depend on the module and projection. Attachment operations should be verified for the target environment.
Martini implementation pattern
Martini implementation pattern: process the parent object first, then call the confirmed attachment endpoint to transfer binary or encoded content and metadata. The workflow should preserve the parent correlation key and handle partial completion separately from the business-object transaction.
Implementation sequence
Common IFS Cloud integration patterns
Pattern 1: Synchronize customers with Salesforce
When to use this pattern
Use this pattern when IFS Cloud owns customer master data or when Salesforce service teams need current customer and contact information. A scheduled workflow or a verified business event can initiate the synchronization, while Salesforce service activity can optionally create or update IFS Cloud Work Orders.
Integration direction
Example Mapping
| IFS Cloud Field | Canonical Field | Target Field |
|---|---|---|
| CustomerNo | customer.externalId | Account.ExternalId |
| Name | customer.name | Account.Name |
| PrimaryContact | customer.primaryContact | Contact.Email |
| Address | customer.address | Account.BillingAddress |
Martini implementation pattern
Martini retrieves changed Customers and related contacts through the relevant projection, maps them to a canonical customer model, validates required identifiers, and upserts Salesforce records. Stable external identifiers and correlation tracking prevent duplicates; transient failures are retried and rejected records are routed for review.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
- scheduled execution
Pattern 2: Exchange purchase orders with SAP S/4HANA
When to use this pattern
Use this pattern when procurement or finance processes span IFS Cloud and SAP S/4HANA. The workflow can send approved IFS Cloud Purchase Orders and return invoice or accounting status while coordinating supplier and part references.
Integration direction
Example Mapping
| IFS Cloud Field | Canonical Field | Target Field |
|---|---|---|
| OrderNo | purchaseOrder.externalId | PurchaseOrder.PurchaseOrder |
| SupplierNo | supplier.externalId | Supplier.Supplier |
| PartNo | line.partId | PurchaseOrderItem.Material |
| Qty | line.quantity | PurchaseOrderItem.OrderQuantity |
Martini implementation pattern
Martini reads approved Purchase Orders, validates supplier and Inventory Parts references, transforms header and line data into SAP API structures, and coordinates dependent calls. The workflow records external identifiers, applies bounded retries, and sends partial or business-rule failures to reconciliation rather than blindly replaying creates.
Martini capabilities used
- workflows
- API consumption
- data mapping
- validation
- orchestration
- error handling
Pattern 3: Create IFS Cloud Work Orders from ServiceNow incidents
When to use this pattern
Use this pattern when ServiceNow incidents or requests that meet defined criteria require physical maintenance or service execution in IFS Cloud. Status, assigned resources, completion details, and costs can be returned to ServiceNow.
Integration direction
Example Mapping
| IFS Cloud Field | Canonical Field | Target Field |
|---|---|---|
| number | serviceRequest.externalId | WorkOrder.SourceReference |
| short_description | serviceRequest.summary | WorkOrder.Description |
| cmdb_ci | serviceRequest.configurationItem | WorkOrder.Asset |
| state | serviceRequest.status | WorkOrder.Status |
Martini implementation pattern
Martini receives or polls qualifying ServiceNow incidents, validates the business criteria, looks up existing correlations, and calls the IFS Cloud Work Order projection when the required operation and permissions are available. The workflow handles uncertain timeouts by checking the external identifier before retrying and publishes status updates back to ServiceNow.
Martini capabilities used
- API exposure
- API consumption
- conditional routing
- data mapping
- idempotency
- retry handling
Pattern 4: Run incremental IFS Cloud order synchronization
When to use this pattern
Use this pattern for large or recurring Sales Order, Purchase Order, Invoice, or Inventory Part synchronizations when business-event coverage is unavailable or insufficient. It uses paging and a durable checkpoint to limit load and make recovery predictable.
Integration direction
Example Mapping
| IFS Cloud Field | Canonical Field | Target Field |
|---|---|---|
| OrderNo | order.externalId | tranId |
| CustomerNo | order.customerId | entity |
| OrderLine.PartNo | line.itemId | item |
| OrderLine.Qty | line.quantity | quantity |
Martini implementation pattern
A scheduled Martini workflow loads the last successful timestamp and page checkpoint, requests ordered IFS Cloud collections, maps each page to the target model, and commits progress only after successful writes. It respects throttling responses, uses bounded concurrency, and reprocesses pages safely through idempotent target logic.
Martini capabilities used
- scheduler triggers
- API consumption
- pagination orchestration
- mapping and transformation
- checkpointing
- error handling
Applications commonly integrated with IFS Cloud
IFS Cloud commonly participates in enterprise landscapes that connect ERP, service, workforce, finance, and customer-facing applications. The exact objects, operations, and ownership model should be confirmed for each deployment and API version.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize IFS Cloud Customers and service information with Salesforce Accounts, Contacts, Cases, or Assets, and create IFS Cloud Work Orders from qualifying service activity. | IFS Cloud → Martini → Salesforce | Martini can consume IFS Cloud projections on a schedule or from supported events, normalize customer and service identifiers, map payloads to Salesforce APIs, and use correlation keys to prevent duplicate Work Orders or Accounts. |
| SAP S/4HANA | Exchange Suppliers, Purchase Orders, invoices, parts, and accounting information between IFS Cloud and SAP S/4HANA. | IFS Cloud → Martini → SAP S/4HANA | A Martini workflow can transform IFS Cloud projection payloads into SAP API structures, coordinate multi-step procurement or financial calls, apply validation, and route failed transactions for reconciliation. |
| ServiceNow | Connect ServiceNow incidents, requests, and configuration information with IFS Cloud Work Orders and service execution data. | ServiceNow → Martini → IFS Cloud | Martini can qualify incoming ServiceNow incidents, create or update IFS Cloud Work Orders through the relevant projection, correlate external identifiers, and return status, resource, completion, and cost information. |
| Microsoft Dynamics 365 | Synchronize IFS Cloud Customers, Sales Orders, Inventory Parts, and invoices with Microsoft Dynamics 365 applications. | Microsoft Dynamics 365 → Martini → IFS Cloud | Martini can normalize identifiers, page through IFS Cloud collections, transform order and customer payloads, and coordinate status updates according to the system-of-record decision. |
| Workday | Exchange worker, organization, project, or cost information so IFS Cloud resources and responsible parties reflect workforce changes. | Workday → Martini → IFS Cloud | A scheduled Martini workflow can process effective-dated changes incrementally, validate organizational references, map workers to IFS Cloud structures, and retain checkpoints for safe reprocessing. |
| NetSuite | Exchange Customers, Sales Orders, invoices, and fulfillment or payment status between NetSuite and IFS Cloud. | NetSuite → Martini → IFS Cloud | Martini can map order lines and identifiers, call the relevant IFS Cloud projections, coordinate fulfillment and invoice updates, and reconcile partial failures with bounded retries and correlation keys. |
How to build a IFS Cloud integration in Martini
Objective
Establish environment-specific access to the IFS Cloud tenant and any target systems without embedding credentials in workflow logic.
Instructions in Martini
- Confirm the IFS Cloud base URL, projection, release, identity provider, scopes, and permissions
- Configure OAuth 2.0, OpenID Connect, or the tenant-approved authentication method
- Store client credentials, tokens, and endpoints as Martini environment secrets
- Test access with a read operation against the selected projection
Objective
Select the trigger that matches the event coverage and consistency requirements of the integration.
Instructions in Martini
- Use a verified IFS Cloud business event or HTTP callback when it provides sufficient coverage
- Expose an authenticated Martini API for supported outbound notifications
- Use a scheduler for incremental polling when event coverage is unavailable or incomplete
- Use messaging infrastructure only when it is supported and configured for the deployment
Objective
Read complete and current IFS Cloud business objects while controlling request volume and preserving recovery state.
Instructions in Martini
- Define projection fields, relationships, filters, ordering, and page size
- Retrieve the current object when an event contains only an identifier
- Use timestamps or another supported change indicator for incremental synchronization
- Persist checkpoints after successful page or object processing
Objective
Coordinate calls, dependencies, routing, and multi-step business processes in a maintainable Martini workflow.
Instructions in Martini
- Separate retrieval, validation, transformation, target writes, and status updates into clear workflow stages
- Use correlation identifiers across IFS Cloud and external systems
- Add conditional routing for business-object status, ownership, and eligibility
- Keep parent-object and attachment processing independently observable
Objective
Convert IFS Cloud projection payloads into canonical and target-specific structures while enforcing data quality.
Instructions in Martini
- Map actual IFS Cloud fields such as CustomerNo, OrderNo, SupplierNo, and PartNo to canonical fields
- Validate required fields, references, dates, quantities, and status transitions
- Normalize identifiers, time zones, enumerations, and address structures
- Apply business rules before submitting create or update operations
Objective
Persist transformed data in downstream systems with safe create, update, and reconciliation behavior.
Instructions in Martini
- Use stable external identifiers or lookup-before-create logic
- Submit target API requests with bounded concurrency
- Record target identifiers and source-to-target correlation values
- Handle partial failures without advancing the checkpoint prematurely
Common IFS Cloud data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Customers | Synchronize customer master data, addresses, contacts, and commercial information. | Salesforce, Microsoft Dynamics 365, NetSuite, SAP S/4HANA | Martini reads or receives Customer data through the relevant projection, normalizes identifiers, maps fields to a canonical customer model, and applies duplicate and validation rules. |
| Suppliers | Exchange supplier master data, contacts, purchasing details, and supplier site information. | SAP S/4HANA, NetSuite, Microsoft Dynamics 365 | Martini can process supplier changes incrementally, validate required purchasing attributes, transform the projection payload, and reconcile rejected updates. |
| Sales Orders | Transfer customer orders, order lines, delivery details, pricing, and fulfillment status. | NetSuite, Microsoft Dynamics 365, Salesforce, SAP S/4HANA | Martini maps order headers and lines, preserves external identifiers, coordinates multi-step calls, and uses idempotent upsert or lookup-before-create logic. |
| Purchase Orders | Exchange procurement orders, purchase lines, supplier information, receipts, and status. | SAP S/4HANA, NetSuite, Microsoft Dynamics 365 | Martini validates supplier and part references, transforms order structures, routes approval or status changes, and retries recoverable API failures. |
| Work Orders | Coordinate maintenance or service work, activities, resources, materials, and execution status. | ServiceNow, Salesforce, Microsoft Dynamics 365 | Martini can create or update Work Orders when the projection and permissions allow it, correlate source incidents or cases, and prevent duplicate creation. |
| Invoices | Exchange customer or supplier invoice data, payment information, and accounting status. | SAP S/4HANA, NetSuite, Microsoft Dynamics 365 | Martini maps invoice lines and financial identifiers, applies business validation, coordinates status updates, and sends exceptions to reconciliation workflows. |
Authentication and security considerations
Token-based authentication
IFS Cloud commonly uses OAuth 2.0 or OpenID Connect with tenant-specific identity-provider configuration. Client credentials suit server-to-server integrations when enabled, while user-context tokens may be required for operations that must respect an individual user's permissions.
Secrets and permissions
Store client credentials, token settings, base URLs, and environment-specific values in Martini secrets and configuration. Access is governed by token scopes and the IFS Cloud permission model assigned to the calling identity.
Transport controls
- Use HTTPS and the tenant-approved API gateway or reverse proxy configuration.
- Confirm issuer, audience, scopes, projection permissions, and network controls for each environment.
- Treat Basic Authentication as a compatibility option only after confirming that it is permitted and appropriate.
Operational considerations for IFS Cloud integrations
Projection and schema control
Confirm projection versions, supported operations, required fields, relationships, custom attributes, status values, and event payloads. Fields visible in the IFS Cloud interface are not necessarily exposed by every projection.
Throughput and pagination
Use bounded page sizes and concurrency. Respect gateway or tenant throttling, including 429 responses and Retry-After values where provided. Incremental filters and durable checkpoints reduce load and improve recovery.
Idempotency and uncertain outcomes
Retries after timeouts can duplicate creates if the original request succeeded. Use stable external identifiers, lookup-before-create logic, correlation values, and duplicate-event protection before replaying unsafe operations.
Release and event testing
Validate integrations against the target release and configuration. Test create, update, status transitions, permissions, event delivery, attachment behavior, schema changes, and partial failures before production deployment.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration instead of isolated scripts
IFS Cloud integrations often require projection discovery, authentication, paging, business-rule validation, related-object calls, and reconciliation. Martini provides a workflow-based place to coordinate these concerns rather than scattering them across scripts.
Reusable transformations
Martini can map IFS Cloud projection payloads into canonical models and target-specific API structures, while reusable workflows and services keep customer, order, invoice, and Work Order logic maintainable.
Operational control
- Choose event-driven processing when a verified business event exists and scheduled polling when it does not.
- Centralize secrets and environment configuration across development, test, and production.
- Apply validation, idempotency, retries, checkpointing, logging, and reconciliation consistently.
Frequently asked questions
IFS Cloud is primarily integrated through REST APIs and OData-style projections for business objects such as Customers, Suppliers, Orders, Invoices, Work Orders, and Inventory Parts. Selected business events may provide notifications through configured callbacks, event channels, or messaging infrastructure. Scheduled incremental synchronization is an alternative when event coverage is unavailable.
Yes. Martini can consume IFS Cloud REST APIs, use tenant-configured OAuth authentication, receive supported HTTP event notifications, expose APIs for inbound integration, and orchestrate mappings, validation, retries, and scheduled synchronization. No native Martini IFS Cloud connector is documented in the supplied research.
No. A dedicated IFS Cloud connector is not required. Martini can integrate using IFS Cloud REST and OData-style projections, supported event or callback mechanisms, configured authentication, and scheduled workflows. SOAP or attachment interfaces should be confirmed for the specific environment before use.
Lonti does not charge an additional per-connector or per-vendor fee to integrate IFS Cloud with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from IFS, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment model.
Start with the relevant IFS Cloud REST projection. Confirm its version, fields, relationships, supported create or update operations, actions, permissions, and business rules. REST projections are the preferred starting point for new integrations; SOAP should be treated as legacy and validated for the target release.
Martini can receive HTTP requests through an exposed API or webhook-oriented workflow when the IFS Cloud deployment provides a supported outbound callback or event delivery path. IFS Cloud event coverage is selected and configuration-specific, not a universal webhook for every object change. Messaging delivery requires the supported protocol for the deployment.
Use paginated REST requests, bounded concurrency, and an incremental filter based on a supported timestamp or change indicator. Persist a durable checkpoint, account for time zones and clock precision, and use idempotent writes so failed pages or uncertain retries can be safely reprocessed.
Martini can map projection payloads into canonical and target-specific models, validate business rules, correlate source and target identifiers, and route failures. Workflows should use bounded retries with backoff for transient errors, inspect uncertain create outcomes before retrying, and protect against duplicate events or concurrent updates with idempotent logic.
Related Martini documentation
Workflows
Connect IFS Cloud with your enterprise systems
Use Martini to build maintainable IFS Cloud integrations around REST projections, verified business events, secure authentication, scheduled synchronization, data mapping, and operational controls.